You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I encountered incorrect behavior while using the data flow analysis with reachableByFlows. The problem is that the analyzer improperly connects methods that are unrelated to each other.
In the code, there is an execute method, which clearly belongs to the Django library and should be recognized as a call to cursor.execute() from Django. However, during analysis, Joern links this method to another execute method located in a different file.
I've experienced the same behavior with built-in methods like string.format(). If there were other methods named format in the project, the analyzer would link them together.
It is clear that the execute method from file1 is in no way related to the execute method from file2,
Screenshots
It's how reproduce this behavior
cpg.call.name("execute").location.l
I also saw in the README that the parser has the following issue: Incorrect instance argument for a call like x.func. Is my problem related to this? Are there any ways to resolve it?
Desktop (please complete the following information):
OS: macOS Sonoma 14.6.1
Joern Version: 4.0.96
Java version: 21.0.4(But I've tried others too)
The text was updated successfully, but these errors were encountered:
Describe the bug
I encountered incorrect behavior while using the data flow analysis with reachableByFlows. The problem is that the analyzer improperly connects methods that are unrelated to each other.
In the code, there is an execute method, which clearly belongs to the Django library and should be recognized as a call to cursor.execute() from Django. However, during analysis, Joern links this method to another execute method located in a different file.
I've experienced the same behavior with built-in methods like string.format(). If there were other methods named format in the project, the analyzer would link them together.
It is clear that the execute method from file1 is in no way related to the execute method from file2,
Screenshots
It's how reproduce this behavior
cpg.call.name("execute").location.l
I also saw in the README that the parser has the following issue: Incorrect instance argument for a call like x.func. Is my problem related to this? Are there any ways to resolve it?
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: