-
Notifications
You must be signed in to change notification settings - Fork 63
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
SAW should respond to SIGINFO
topics: error-messages
Issues involving the messages SAW produces on error
type: feature request
Issues requesting a new feature or capability
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
Systematize error-issuing and other printing functions
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
#2129
opened Oct 12, 2024 by
sauclovian-g
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
#2128
opened Oct 12, 2024 by
sauclovian-g
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
#2126
opened Oct 4, 2024 by
mccleeary-galois
1 task
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
#2122
opened Sep 13, 2024 by
sauclovian-g
Printing of Cryptol newtypes in counterexamples throws away too much information
subsystem: cryptol-saw-core
Issues related to Cryptol -> saw-core translation with cryptol-saw-core
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
usability
An issue that impedes efficient understanding and use
#2119
opened Sep 10, 2024 by
sauclovian-g
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
#2111
opened Aug 28, 2024 by
weaversa
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
#2109
opened Aug 27, 2024 by
sauclovian-g
Bogus stack trace with MIR verification and wrong return type
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
#2108
opened Aug 27, 2024 by
sauclovian-g
Internal errors are not just impossible executions
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
usability
An issue that impedes efficient understanding and use
#2106
opened Aug 24, 2024 by
sauclovian-g
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
#2105
opened Aug 23, 2024 by
sauclovian-g
llvm_verify
crashes (Prelude.tail: empty list
) when verifying a function whose name contains "__breakpoint__
" without a #
afterwards
subsystem: crucible-llvm
#2097
opened Aug 21, 2024 by
RyanGlScott
Heapster: Issues specifically related to memory verification using Heapster
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
#2096
opened Aug 21, 2024 by
RyanGlScott
Clearly specify the behavior of Issues related to LLVM bitcode verification with crucible-llvm
type: enhancement
Issues describing an improvement to an existing feature or capability
llvm_extract
/llvm_compositional_extract
with respect to global variables
subsystem: crucible-llvm
#2093
opened Aug 16, 2024 by
RyanGlScott
Support Issues related to Java verification with crucible-jvm
subsystem: crucible-llvm
Issues related to LLVM bitcode verification with crucible-llvm
subsystem: saw-remote-api
Issues related to the SAW server and its RPC bindings
type: feature request
Issues requesting a new feature or capability
llvm_extract
, llvm_compositional_extract
, jvm_extract
, etc. in the Python bindings
subsystem: crucible-jvm
#2092
opened Aug 16, 2024 by
RyanGlScott
llvm_compositional_extract
: surprising lack of return type detection
subsystem: crucible-llvm
#2091
opened Aug 16, 2024 by
RyanGlScott
saw should be repeatable, or have a repeatable mode
tooling: test infrastructure
Issues involving test infrastructure or test execution, or making SAW more testable
type: enhancement
Issues describing an improvement to an existing feature or capability
#2090
opened Aug 13, 2024 by
sauclovian-g
2 tasks
Reduce the use of the Issues describing an improvement to an existing feature or capability
type: feature request
Issues requesting a new feature or capability
fix
function in the Cryptol->SAWCore translation
type: enhancement
#2089
opened Aug 13, 2024 by
RyanGlScott
Make Issues describing an improvement to an existing feature or capability
type: feature request
Issues requesting a new feature or capability
summarize_verification
report whether definitions depend on unsafe primitives or axioms (e.g., fix
)
type: enhancement
#2088
opened Aug 13, 2024 by
RyanGlScott
MIR counterparts to Issues related to Rust verification with crucible-mir and/or mir-json
type: enhancement
Issues describing an improvement to an existing feature or capability
type: feature request
Issues requesting a new feature or capability
llvm_extract
and llvm_compositional_extract
subsystem: crucible-mir
#2085
opened Aug 7, 2024 by
RyanGlScott
Define a Issues requesting a new feature or capability
map
function (like for
, but non-monadic)
type: feature request
#2083
opened Jul 31, 2024 by
RyanGlScott
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
#2082
opened Jul 31, 2024 by
sauclovian-g
Previous Next
ProTip!
Follow long discussions with comments:>50.