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

421 Open 729 Closed
421 Open 729 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

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
#2169 opened Dec 20, 2024 by sauclovian-g 2025T1
Make the warnings introduced by #2162 into errors easy Issues that are expected to be easy to resolve and might therefore be good for new contributors 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
#2167 opened Dec 20, 2024 by sauclovian-g Someday
2
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
#2166 opened Dec 19, 2024 by sauclovian-g 2025T1
2
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
#2164 opened Dec 17, 2024 by sauclovian-g 2025T1
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
#2163 opened Dec 17, 2024 by sauclovian-g 2025T1
@sauclovian-g
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
#2162 opened Dec 17, 2024 by sauclovian-g 2024T3
@sauclovian-g
1
write_goal only writes the last proof goal to a file, unlike other goal-writing proof scripts subsystem: saw-core Issues related to the saw-core representation or the saw-core subsystem type: bug Issues reporting bugs or unexpected/unwanted behavior
#2160 opened Dec 12, 2024 by RyanGlScott 2025T1
2
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
#2159 opened Dec 12, 2024 by sauclovian-g 2024T3
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
#2158 opened Dec 12, 2024 by sauclovian-g 2025T1
@sauclovian-g
1
SAW User Manual Issues and Recommendations documentation Issues involving documentation type: enhancement Issues describing an improvement to an existing feature or capability usability An issue that impedes efficient understanding and use
#2156 opened Dec 9, 2024 by smithdtyler 2024T3
2
Support implications as rewrite rules subsystem: saw-core Issues related to the saw-core representation or the saw-core subsystem type: feature request Issues requesting a new feature or capability usability An issue that impedes efficient understanding and use
#2155 opened Dec 5, 2024 by mrogers67
4
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
1
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
ProTip! Type g i on any issue or pull request to go back to the issue listing page.