Fix self-referencing issue in getMethodSignatureInSubClass
at ICFGDotExporter
#920
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
In the current implementation of
getMethodSignatureInSubClass
withinICFGDotExporter.java
, there's a logical oversight where the method could potentially include the target method in its own set of sub-class method signatures. This leads to the incorrect behavior inconnectEdgesToSubClasses
, where a method might connect an edge from its starting statement back to itself, causing confusion in the call graph visualization.Before applying the PR change:
source in
connectEdgesToSubClasses
:Here result
methodSignatureInSubClass
will containstarget
sink in
connectEdgesToSubClasses
:which will also overwrite previous entry set where call the
connectEdgesToSubClasses
incomputeCalls
Solution
This PR addresses the issue by adding an additional check in the
filter
operation withingetMethodSignatureInSubClass
. The updated logic ensures that the target method signature is explicitly excluded from the set of callable sub-class signatures.Changes Made
target
from the results if it matches thesource
.Thank you for considering this fix to improve the accuracy of our tool.