Skip to content
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

Report dependencies of markers #46

Open
reprogrammer opened this issue Feb 7, 2013 · 0 comments
Open

Report dependencies of markers #46

reprogrammer opened this issue Feb 7, 2013 · 0 comments
Assignees
Milestone

Comments

@reprogrammer
Copy link
Owner

LCK06J and VNA00J propagate unsafe instructions along the call graph. However, the markers reported by Keshmesh do not include sufficient information to discover the root cause each marker. One possibility would be to include the immediate neighboring call graph nodes that propagated unsafe instructions to each marker. For example, in the following piece of code, the marker at line 2 would include references to the instructions at lines 5 and 6. Likewise, the marker at line 6 would refer to the instruction at line 9.

 1: m1() {
 2:  m2();
 3: }
 4: m2() {
 5:  shareVariable1++;
 6:  m3();
 7: }
 8: m3() {
 9:  shareVariable2++
10: }
@ghost ghost assigned reprogrammer Feb 7, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant