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

[BUG] Heap analyses should react to type conversions and castings #300

Closed
lucaneg opened this issue Dec 11, 2023 · 0 comments · Fixed by #314
Closed

[BUG] Heap analyses should react to type conversions and castings #300

lucaneg opened this issue Dec 11, 2023 · 0 comments · Fixed by #314
Assignees
Labels
‼ priority:p1 Priority planning - level 1 🎊 resolution:resolved Bug or feature resolved - might not have been merged to master yet 🔍 scope:analysis Work regarding abstract domains or fixpoint algorithms 🐛 type:bug Something isn't working
Milestone

Comments

@lucaneg
Copy link
Member

lucaneg commented Dec 11, 2023

Description
Sometimes, to explicitly invoke a method from a superclass (e.g., super.foo()), the receiver of the call can be set to (Superclass) this, that is, the current object casted to its supertype. Logic inside heap abstractions should support expressions of this kind: e.g., at

rhs might be a BinaryExpression with a TypeConv operator.

@lucaneg lucaneg added 🐛 type:bug Something isn't working ‼ priority:p1 Priority planning - level 1 🔍 scope:analysis Work regarding abstract domains or fixpoint algorithms labels Dec 11, 2023
@lucaneg lucaneg added this to the 0.1 milestone Dec 11, 2023
@lucaneg lucaneg self-assigned this Dec 11, 2023
@lucaneg lucaneg added this to LiSA Dec 11, 2023
@lucaneg lucaneg moved this to Todo in LiSA Dec 11, 2023
@lucaneg lucaneg moved this from Todo to Backlog in LiSA Dec 11, 2023
@lucaneg lucaneg moved this from Backlog to Todo in LiSA Jul 31, 2024
@lucaneg lucaneg moved this from Todo to In Progress in LiSA Aug 1, 2024
lucaneg added a commit that referenced this issue Aug 1, 2024
lucaneg added a commit that referenced this issue Aug 1, 2024
@lucaneg lucaneg added the 🎊 resolution:resolved Bug or feature resolved - might not have been merged to master yet label Aug 1, 2024
@lucaneg lucaneg moved this from In Progress to Done in LiSA Aug 1, 2024
@lucaneg lucaneg mentioned this issue Aug 1, 2024
@github-project-automation github-project-automation bot moved this from Done to Merged in LiSA Aug 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
‼ priority:p1 Priority planning - level 1 🎊 resolution:resolved Bug or feature resolved - might not have been merged to master yet 🔍 scope:analysis Work regarding abstract domains or fixpoint algorithms 🐛 type:bug Something isn't working
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant