-
-
Notifications
You must be signed in to change notification settings - Fork 709
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
Soot resolved an incorrect method signautre #2021
Comments
There is a similar problem when analyzing the following method: <com.fasterxml.jackson.core.io.ContentReference: com.fasterxml.jackson.core.io.ContentReference 'unknown'()> |
This happens when the method name is a reserved name in Jimple: soot/src/main/java/soot/Scene.java Line 1535 in 8698b75
Otherwise we would have a problem when you write out Jimple files and try to read them back in. See the |
look here, same problem: #1697 |
@MarcMil Thanks for your kind reply. Yes, I know Soot has the reserved names. However, the method For the following two used method signatures: 1st signature 2nd signature The first signature can be converted to (annotation -> 'annotation'), but we cannot get the quoted version (with -> 'with') of the second signuatre when invoke Soot may only use dot to seperate the given name, however, we often use method signature to get a resovled And, another problem is, not all reserved names will be changed to quoted version, e.g., |
Describe the bug
I used Soot to analyze some real-world projects, and found it provides an incorrect method signature, which has redundant single quotes.
Input file
Maven Repo Link
The correct signature should be:
com.fasterxml.jackson.core.util.JacksonFeatureSet: com.fasterxml.jackson.core.util.JacksonFeatureSet with(com.fasterxml.jackson.core.util.JacksonFeature)
However, I got the incorrect results with redudant single quotes in the method name.
To reproduce
Directly use Soot analyze this class file and retrieve the method signature:
The text was updated successfully, but these errors were encountered: