Escapes via `memcpy` are ignored
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by running Goblint on the C reproducer with the shown analysis parameters, then trace the memcpy and modify path that leads to the Apron.Manager.Error. Done means this case is handled without the reported crash and the final __goblint_check result is produced.
Written by the indexing model from the issue text.
Description
For what it's worth, I tried to prompt AI to poke holes in the code for counterexamples in #2100, and (before the session got derailed by cybersecurity guardrails) it got me the following adjacent case:
// PARAM: --set ana.activated[+] apron --enable ana.sv-comp.functions
#include <goblint.h>
#include <string.h>
static int *target;
static void modify(void) {
*target = __VERIFIER_nondet_int();
}
int main(void) {
int left = __VERIFIER_nondet_int();
int right = left;
int *source = &right;
memcpy(&target, &source, sizeof(target));
modify();
__goblint_check(left == right); // UNKNOWN!
}
which crashes Goblint with
Fatal error: exception Apron.Manager.Error
{ exn = Exc_invalid_argument; funid = Funid_assign_texpr_array;
msg = unknown variable right#671 in the environment; }
Given that the failure is different from the original one, I am approving this pull request.
Originally posted by @jprotopopov-ut in https://github.com/goblint/analyzer/issues/2100#issuecomment-5292729594
- Dominant language
- OCaml
- Stars
- 252
- Forks
- 90
- Avg merge
- 4d 1m
- Merged PRs (30d)
- 19
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from goblint/analyzer
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
good first issue precision
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
usability
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
precision student-job unsound
Difficulty 5/5 Over a week Newbie friendliness 45/100
-
sv-comp unsound
Difficulty 4/5 3-5 days Newbie friendliness 42/100
All issues in goblint/analyzer
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
bancolombia/sentinel#20 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
chore
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
alunduil/woodland-generators#669 ·
-
area: tooling
Difficulty 2/5 1-3 hours Newbie friendliness 86/100