Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
S
seer
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Nils Fitinghoff
seer
Commits
4fcbb21a
Commit
4fcbb21a
authored
7 years ago
by
David Renshaw
Browse files
Options
Downloads
Patches
Plain Diff
tweak wording in readme
parent
2b026cc7
Branches
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+9
-9
9 additions, 9 deletions
README.md
with
9 additions
and
9 deletions
README.md
+
9
−
9
View file @
4fcbb21a
...
@@ -7,15 +7,15 @@ Seer is a fork of [miri](https://github.com/solson/miri)
...
@@ -7,15 +7,15 @@ Seer is a fork of [miri](https://github.com/solson/miri)
that adds support for symbolic execution, using
that adds support for symbolic execution, using
[
z3
](
https://github.com/Z3Prover/z3
)
as a solver backend.
[
z3
](
https://github.com/Z3Prover/z3
)
as a solver backend.
Given a program, Seer attempts to exhaustively
Given a program
written in Rust
, Seer attempts to exhaustively
enumerate the possible execution paths through t
hat program
.
enumerate the possible execution paths through
i
t.
Seer represents program input in a _symbolic_ form
To achieve this,
Seer represents
the
program
's
input in a _symbolic_ form
,
and
maintain
s
a set of constraints on it.
maintain
ing
a set of constraints on it.
When Seer reaches a branch
ing
point in the program, it
When Seer reaches a branch point in the program, it
invokes its solver backend to compute which
branche
s
invokes its solver backend to compute which
continuation
s
are
fea
sible given the current constraints. The
fea
sible
are
pos
sible given the current constraints. The
pos
sible
branche
s are then enqueued for exploration, augmented with the
continuation
s are then enqueued for exploration, augmented with the
new constraints learned from the branch
ing
condition.
respective
new constraints learned from the branch condition.
Seer considers any bytes read in through
`::std::io::stdin()`
Seer considers any bytes read in through
`::std::io::stdin()`
as symbolic input. This means that once
as symbolic input. This means that once
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment