We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Fatal error: exception Failure("Node.move_opt: ambiguous moved index")
On top of #1234 with path-sensitive MemLeak analysis, the generation of witnesses fails with an error message
The reduced program (with a manual config e.g. without autotuning and loop unrolling (so unrelated to #1225)) is the following:
//PARAM: --enable witness.graphml.enabled --enable ana.sv-comp.functions --enable ana.sv-comp.enabled --sets ana.specification /home/michael/Documents/sv-comp/sv-benchmarks/c/properties/valid-memsafety.prp --sets ana.activated[+] "memLeak" --set ana.malloc.unique_address_count 1 struct _twoIntsStruct { int intOne ; int intTwo ; }; typedef struct _twoIntsStruct twoIntsStruct; void printStructLine(twoIntsStruct const *structTwoIntsStruct) { return; } int main(int argc, char **argv) { twoIntsStruct *data; int tmp_1; if (tmp_1 != 0) { twoIntsStruct *dataBuffer = malloc(800UL); data = dataBuffer; } else { twoIntsStruct *dataBuffer_0 = malloc(800UL); data = dataBuffer_0; } printStructLine((twoIntsStruct const *)data); free((void *)data); return; }
The problem seems to be related to the call of printStructLine, so I started wondering if the issue has to do with path-sensitivity...
printStructLine
We should probably aim to fix this or at least return trivial witnesses in such cases to still get points if fixing is out-of-reach.
The text was updated successfully, but these errors were encountered:
Add test from #1235
4279417
Remove CFG-based function return node from MyARG.Stack (closes #1235)
23771e4
sim642
Successfully merging a pull request may close this issue.
On top of #1234 with path-sensitive MemLeak analysis, the generation of witnesses fails with an error message
The reduced program (with a manual config e.g. without autotuning and loop unrolling (so unrelated to #1225)) is the following:
The problem seems to be related to the call of
printStructLine
, so I started wondering if the issue has to do with path-sensitivity...We should probably aim to fix this or at least return trivial witnesses in such cases to still get points if fixing is out-of-reach.
The text was updated successfully, but these errors were encountered: