-
Notifications
You must be signed in to change notification settings - Fork 62
Issues: GaloisInc/saw-script
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Invalid logic in s2n tls proof
tech debt
Issues that document or involve technical debt
test assets
Issues involving test programs or other test assets
tooling: CI
Issues involving CI/CD scripts or processes
type: bug
Issues reporting bugs or unexpected/unwanted behavior
CI is breaking on archaic downloads
tech debt
Issues that document or involve technical debt
test assets
Issues involving test programs or other test assets
tooling: CI
Issues involving CI/CD scripts or processes
type: bug
Issues reporting bugs or unexpected/unwanted behavior
Cannot embed Cryptol newtypes in let {{ }}
missing cryptol features
Issues about features in Cryptol that don't work in SAW
needs test
Issues for which we should add a regression test
type: bug
Issues reporting bugs or unexpected/unwanted behavior
Builtin vs. hardcoded types
needs test
Issues for which we should add a regression test
tech debt
Issues that document or involve technical debt
type: bug
Issues reporting bugs or unexpected/unwanted behavior
Oddities of top-level binds
tech debt
Issues that document or involve technical debt
type: bug
Issues reporting bugs or unexpected/unwanted behavior
usability
An issue that impedes efficient understanding and use
write_goal
only writes the last proof goal to a file, unlike other goal-writing proof scripts
subsystem: saw-core
Deprecate llvm_struct()
better-when-documented
Issues whose root causes include missing or wrong documentation
documentation
Issues involving documentation
easy
Issues that are expected to be easy to resolve and might therefore be good for new contributors
subsystem: crucible-llvm
Issues related to LLVM bitcode verification with crucible-llvm
tech debt
Issues that document or involve technical debt
type: bug
Issues reporting bugs or unexpected/unwanted behavior
usability
An issue that impedes efficient understanding and use
saw-script interpreter typechecks one line at a time
needs design
Technical design work is needed for issue to progress
tech debt
Issues that document or involve technical debt
type: bug
Issues reporting bugs or unexpected/unwanted behavior
MIR Technical design work is needed for issue to progress
subsystem: crucible-mir
Issues related to Rust verification with crucible-mir and/or mir-json
type: bug
Issues reporting bugs or unexpected/unwanted behavior
bool
arrays are cumbersome to use in SAW
needs design
Reading a static mutable reference crashes with empty mux tree
needs test
Issues for which we should add a regression test
subsystem: crucible-mir
Issues related to Rust verification with crucible-mir and/or mir-json
topics: error-handling
Issues involving the way SAW responds to an error condition
topics: error-messages
Issues involving the messages SAW produces on error
type: bug
Issues reporting bugs or unexpected/unwanted behavior
usability
An issue that impedes efficient understanding and use
Unhelpful empty counterexample
easy
Issues that are expected to be easy to resolve and might therefore be good for new contributors
topics: error-handling
Issues involving the way SAW responds to an error condition
topics: error-messages
Issues involving the messages SAW produces on error
type: bug
Issues reporting bugs or unexpected/unwanted behavior
usability
An issue that impedes efficient understanding and use
saw-core position reporting doesn't print correctly
needs test
Issues for which we should add a regression test
topics: error-messages
Issues involving the messages SAW produces on error
type: bug
Issues reporting bugs or unexpected/unwanted behavior
Position tracking by global variable isn't robust
tech debt
Issues that document or involve technical debt
topics: error-handling
Issues involving the way SAW responds to an error condition
topics: error-messages
Issues involving the messages SAW produces on error
type: bug
Issues reporting bugs or unexpected/unwanted behavior
Signatures not shown on Downloads Page but mentioned
documentation
Issues involving documentation
type: bug
Issues reporting bugs or unexpected/unwanted behavior
usability
An issue that impedes efficient understanding and use
Execution of impossible paths during verification
performance
Issues that involve or include performance problems
subsystem: crucible-mir
Issues related to Rust verification with crucible-mir and/or mir-json
tech debt
Issues that document or involve technical debt
type: bug
Issues reporting bugs or unexpected/unwanted behavior
Typechecker gap in mir_assert
needs test
Issues for which we should add a regression test
subsystem: crucible-mir
Issues related to Rust verification with crucible-mir and/or mir-json
topics: error-handling
Issues involving the way SAW responds to an error condition
topics: error-messages
Issues involving the messages SAW produces on error
type: bug
Issues reporting bugs or unexpected/unwanted behavior
usability
An issue that impedes efficient understanding and use
Better synchronize SAW with the High-priority issues
subproject
Issues involving one of the various subprojects SAW depends on
subsystem: crucible-mir
Issues related to Rust verification with crucible-mir and/or mir-json
type: bug
Issues reporting bugs or unexpected/unwanted behavior
mir-json
version it depends on
priority
The repository README should mention the docker images
documentation debt
Documentation tasks previously deferred, postponed, etc.; technical debt in documentation
documentation
Issues involving documentation
type: bug
Issues reporting bugs or unexpected/unwanted behavior
Bogus stack trace with MIR verification and wrong return type
needs test
Issues for which we should add a regression test
topics: error-handling
Issues involving the way SAW responds to an error condition
topics: error-messages
Issues involving the messages SAW produces on error
type: bug
Issues reporting bugs or unexpected/unwanted behavior
Typechecker gap with record argument types
needs test
Issues for which we should add a regression test
tech debt
Issues that document or involve technical debt
topics: error-handling
Issues involving the way SAW responds to an error condition
topics: error-messages
Issues involving the messages SAW produces on error
type: bug
Issues reporting bugs or unexpected/unwanted behavior
unsoundness
Issues that can lead to unsoundness or false verification
llvm_verify
crashes (Prelude.tail: empty list
) when verifying a function whose name contains "__breakpoint__
" without a #
afterwards
subsystem: crucible-llvm
Heapster: Issues specifically related to memory verification using Heapster
topics: error-handling
Issues involving the way SAW responds to an error condition
topics: error-messages
Issues involving the messages SAW produces on error
type: bug
Issues reporting bugs or unexpected/unwanted behavior
Prelude.head: empty list
crash when invoking heapster_typecheck_mut_funs
on empty list
subsystem: heapster
llvm_compositional_extract
: surprising lack of return type detection
subsystem: crucible-llvm
saw inappropriately expands symbolic links
tooling: test infrastructure
Issues involving test infrastructure or test execution, or making SAW more testable
topics: error-messages
Issues involving the messages SAW produces on error
type: bug
Issues reporting bugs or unexpected/unwanted behavior
usability
An issue that impedes efficient understanding and use
There should be a way to clean the test suite
tech debt
Issues that document or involve technical debt
tooling: build system
Issues involving SAW's build system
tooling: test infrastructure
Issues involving test infrastructure or test execution, or making SAW more testable
type: bug
Issues reporting bugs or unexpected/unwanted behavior
Previous Next
ProTip!
Exclude everything labeled
bug
with -label:bug.