[Soot-list] Soot crashes with use-original-names option enabled in whole program mode

Phil Pratt-Szeliga pcpratts at syr.edu
Wed May 2 10:41:09 EDT 2012


Hello,

I will look into this today, it is on my todo list. I just have some
things I need to do first.

Phil Pratt-Szeliga
Syracuse University.

On Wed, May 2, 2012 at 10:18 AM, Longwen Lu <longwenlu at gmail.com> wrote:
> Sorry, forget to attach the command line in the first mail:
> (I omit the -cp option for clarity)
> -main-class VelocityMainClass_5 -pp -w -app -p jb use-original-names:true
> -keep-line-number -no-bodies-for-excluded -process-dir velocity_main/
> -process-dir velocity-1.7_5.jar
>
> On Wed, May 2, 2012 at 4:24 PM, Longwen Lu <longwenlu at gmail.com> wrote:
>>
>> Hello All,
>>
>> An runtime exception occurs when soot runs in whole program mode with
>> option
>> use-original-names enabled.
>>
>> Soot started on Wed May 02 14:00:33 CST 2012
>> Warning: java.dyn.InvokeDynamic is a phantom class!
>> [Call Graph] For information on where the call graph may be incomplete,
>> use the verbose option to the cg phase.
>> Exception in thread "main" java.lang.RuntimeException: Unhandled type
>> bottom_type
>>     at soot.FastHierarchy.canStoreType(FastHierarchy.java:222)
>>
>>     at
>> soot.jimple.toolkits.callgraph.VirtualCalls.resolve(VirtualCalls.java:89)
>>     at
>> soot.jimple.toolkits.callgraph.VirtualCalls.resolve(VirtualCalls.java:83)
>>     at
>> soot.jimple.toolkits.callgraph.OnFlyCallGraphBuilder.addType(OnFlyCallGraphBuilder.java:453)
>>     at
>> soot.jimple.toolkits.callgraph.CallGraphBuilder.build(CallGraphBuilder.java:94)
>>     at
>> soot.jimple.toolkits.callgraph.CHATransformer.internalTransform(CHATransformer.java:43)
>>     at soot.SceneTransformer.transform(SceneTransformer.java:39)
>>     at soot.Transform.apply(Transform.java:89)
>>     at soot.RadioScenePack.internalApply(RadioScenePack.java:57)
>>     at
>> soot.jimple.toolkits.callgraph.CallGraphPack.internalApply(CallGraphPack.java:47)
>>     at soot.Pack.apply(Pack.java:114)
>>     at soot.PackManager.runWholeProgramPacks(PackManager.java:417)
>>     at soot.PackManager.runPacks(PackManager.java:336)
>>     at soot.Main.run(Main.java:198)
>>     at soot.Main.main(Main.java:141)
>>
>> This problem seems easy to reproduce. The exception occurs anyway even I
>> have removed
>> all custom transformers and used different files for analysis.
>> The version of soot used is 2.5.0. Soot works well if I use only one of
>> these two options separately.
>> I find a related bug in soot's bugzilla:
>> https://svn.sable.mcgill.ca/bugzilla/show_bug.cgi?id=109
>> But this bug seems to remain unfixed. And changing to Oracle`s Java SDK
>> 1.6 does not help to
>> solve this problem.
>>
>> Does anyone know how to solve this problem?
>>
>>
>> longwen
>>
>


More information about the Soot-list mailing list