[Soot-list] A flexible no-bodies option?

Marc-Andre Laverdiere-Papineau marc-andre.laverdiere-papineau at polymtl.ca
Thu Jun 28 07:40:47 EDT 2012


Good morning,

I am running 2.5. I am not running soot from the Main because I need to 
detect the entry points.

I realize that there might be a better way to meet my requirement 
though. Would you advise to make a patch for the code that finds the 
entry points instead? Which classes would need a tweak?

Because it is a longish code snippet, I've put it on Pastebin.
http://pastebin.com/Ym5ceESM

Regards,
-- 
Marc-André Laverdière-Papineau
Étudiant au doctorat - PhD Student

On 06/28/2012 12:50 AM, Eric Bodden wrote:
> Hello.
>
>> I am using a whole program analysis with a lot of exclusions. Running
>> spark I get this error:
>>
>> Exception in thread "main" java.lang.RuntimeException: This operation
>> requires resolving level HIERARCHY but sun.misc.ClassFileTransformer is
>> at resolving level DANGLING
>> If you are extending Soot, try to add the following call before calling
>> soot.Main.main(..):
>> Scene.v().addBasicClass(sun.misc.ClassFileTransformer,HIERARCHY);
>>
>> I understand from previous mailing list messages that this would be due
>> to the fact that I am allowing no bodies for excluded.
>
> Even with that option enabled you should not see this error. That's
> the whole point of having that option.
>
> Are you using 2.5.0 or the build from the master branch? In the latter
> we indeed discovered a bug giving such behavior which we are currently
> fixing. If you are using 2.5.0, can you let us know how you invoke
> Soot?
>
> Cheers,
> Eric
>







More information about the Soot-list mailing list