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.

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

Jump to bottom

[BUG] Open calls delete all aliases #194

Closed
lucaneg opened this issue Mar 9, 2022 · 0 comments · Fixed by #195
Closed

[BUG] Open calls delete all aliases #194

lucaneg opened this issue Mar 9, 2022 · 0 comments · Fixed by #195
Assignees
@lucaneg
Labels
⁉ priority:p2 Priority planning - level 2 🎊 resolution:resolved Bug or feature resolved - might not have been merged to master yet 🔍 scope:analysis Work regarding abstract domains or fixpoint algorithms 🌍 scope:interproc Work regarding interprocedural analyses or call graphs 🐛 type:bug Something isn't working
Milestone
0.1b6

Comments

@lucaneg
Copy link
Member

lucaneg commented Mar 9, 2022

Description
Open calls (and, in general, invoking top() or bottom() on the analysis state) cause all stored aliases to vanish, meaning that LiSA will likely fail to resolve subsequent calls.
@lucaneg lucaneg added 🐛 type:bug Something isn't working ⁉ priority:p2 Priority planning - level 2 🔍 scope:analysis Work regarding abstract domains or fixpoint algorithms 🌍 scope:interproc Work regarding interprocedural analyses or call graphs labels Mar 9, 2022
@lucaneg lucaneg added this to the 0.1b6 milestone Mar 9, 2022
@lucaneg lucaneg self-assigned this Mar 9, 2022
@lucaneg lucaneg added the 🎊 resolution:resolved Bug or feature resolved - might not have been merged to master yet label Mar 17, 2022
lucaneg added a commit that referenced this issue Mar 17, 2022
@lucaneg
#194 deleted AnalysisState constructor that didn't accept aliasing
4789a53 
This requires any manual creation of an AnalysisState, like the one
happening in the semantics of CallWithResult, to specify the aliasing.
@lucaneg lucaneg mentioned this issue Mar 17, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lucaneg lucaneg

Labels
⁉ priority:p2 Priority planning - level 2 🎊 resolution:resolved Bug or feature resolved - might not have been merged to master yet 🔍 scope:analysis Work regarding abstract domains or fixpoint algorithms 🌍 scope:interproc Work regarding interprocedural analyses or call graphs 🐛 type:bug Something isn't working
Projects
None yet
Milestone
0.1b6
Development

Successfully merging a pull request may close this issue.

March bugfixing lisa-analyzer/lisa
1 participant
@lucaneg