Skip to content

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.

Sign up for GitHub

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

411 Open 726 Closed
411 Open 726 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

MIR bool arrays are cumbersome to use in SAW needs design 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
#2147 opened Nov 11, 2024 by RyanGlScott 2025T1
3
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
#2145 opened Nov 7, 2024 by sauclovian-g 2024T3
1
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
#2144 opened Nov 7, 2024 by sauclovian-g 2024T3
1
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
#2143 opened Nov 5, 2024 by sauclovian-g Someday
1
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
#2140 opened Nov 2, 2024 by sauclovian-g 2024T3
@sauclovian-g
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 type: enhancement Issues describing an improvement to an existing feature or capability
#2129 opened Oct 12, 2024 by sauclovian-g 2024T3
@sauclovian-g
1
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
#2128 opened Oct 12, 2024 by sauclovian-g 2025T1
@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
2024T3
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
#2124 opened Sep 19, 2024 by sauclovian-g 2025T1
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 2025T1
2
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 2025T1
4
Better synchronize SAW with the mir-json version it depends on priority 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
#2111 opened Aug 28, 2024 by weaversa 2025T1
@RyanGlScott @mccleeary-galois
4
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 2024T3
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
#2108 opened Aug 27, 2024 by sauclovian-g 2024T3
1
Internal errors are not just impossible executions 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 usability An issue that impedes efficient understanding and use
#2106 opened Aug 24, 2024 by sauclovian-g 2025T1
2
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 2024T3
@sauclovian-g
1
Verifying C written with C11 features using SAW type: support Issues that are primarily support requests
#2099 opened Aug 22, 2024 by pennyannn
8
llvm_verify crashes (Prelude.tail: empty list) when verifying a function whose name contains "__breakpoint__" without a # afterwards subsystem: crucible-llvm Issues related to LLVM bitcode verification with crucible-llvm 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
#2097 opened Aug 21, 2024 by RyanGlScott 2025T1
Heapster: Prelude.head: empty list crash when invoking heapster_typecheck_mut_funs on empty list subsystem: 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
#2096 opened Aug 21, 2024 by RyanGlScott 2025T1
Clearly specify the behavior of llvm_extract/llvm_compositional_extract with respect to global variables subsystem: crucible-llvm Issues related to LLVM bitcode verification with crucible-llvm type: enhancement Issues describing an improvement to an existing feature or capability
#2093 opened Aug 16, 2024 by RyanGlScott 2025T1
Support llvm_extract, llvm_compositional_extract, jvm_extract, etc. in the Python bindings subsystem: crucible-jvm Issues related to Java verification with crucible-jvm subsystem: crucible-llvm Issues related to LLVM bitcode verification with crucible-llvm subsystem: saw-python Related to the Python bindings for the RPC SAW server subsystem: saw-remote-api Issues related to the SAW server and its RPC bindings type: feature request Issues requesting a new feature or capability
#2092 opened Aug 16, 2024 by RyanGlScott 2025T1
llvm_compositional_extract: surprising lack of return type detection subsystem: crucible-llvm Issues related to LLVM bitcode verification with crucible-llvm type: bug Issues reporting bugs or unexpected/unwanted behavior
#2091 opened Aug 16, 2024 by RyanGlScott 2025T1
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
2025T1
Reduce the use of the fix function in the Cryptol->SAWCore translation subsystem: cryptol-saw-core Issues related to Cryptol -> saw-core translation with cryptol-saw-core type: feature request Issues requesting a new feature or capability unsoundness Issues that can lead to unsoundness or false verification
#2089 opened Aug 13, 2024 by RyanGlScott 2025T1
1
Make summarize_verification report whether definitions depend on unsafe primitives or axioms (e.g., fix) type: feature request Issues requesting a new feature or capability unsoundness Issues that can lead to unsoundness or false verification
#2088 opened Aug 13, 2024 by RyanGlScott 2025T1
ProTip! Mix and match filters to narrow down what you’re looking for.