[prev in list] [next in list] [prev in thread] [next in thread] 

List:       soot-list
Subject:    [Soot-list] question about
From:       bodden () st ! informatik ! tu-darmstadt ! de (Eric Bodden)
Date:       2010-03-22 7:22:35
Message-ID: 804e3c661003220022x14c5bdb2sd19c55b7ff7b99d2 () mail ! gmail ! com
[Download RAW message or body]

Hello.

It's hard to say what's causing this without seeing the code that you
are analyzing. You should probably wait for the new Soot release
(should be available within a week) and then try again. Maybe it's
some bug that has been fixed in the meantime.

Eric

--
Dr. Eric Bodden
Software Technology Group, Technische Universit?t Darmstadt, Germany
Tel: +49 6151 16-5478    Fax: +49 6151 16-5410
Mailing Address: S2|02 A209, Hochschulstra?e 10, 64289 Darmstadt



On 21 March 2010 17:36, k3e huan <k3e.huan at gmail.com> wrote:
> Hi,
> ? I met a problem when I was trying to use Soot analyze one GWT sample
> application (the one that is generated automatically by its
> "webAppCreator.cmd" ). I have tried my best to solve this but no lucky yet.
> ? The problem is: when I was trying to generate jimple file from Java source
> code in Eclipse (with Soot plug-in installed), it reports an exception:
> java.lang.reflect.InvocationTargetException.
> ? Following is the log message:
>
> Soot started on Sun Mar 21 12:17:55 EDT 2010
> No main class given. Inferred 'com.zkh.gwt.test2.client.Test2' as main
> class.
> [Call Graph] For information on where the call graph may be incomplete, use
> the verbose option to the cg phase.
> java.lang.reflect.InvocationTargetException
> ??? at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ??? at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> ??? at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> ??? at java.lang.reflect.Method.invoke(Method.java:597)
> ??? at ca.mcgill.sable.soot.launching.SootThread.run(SootThread.java:138)
> Caused by: java.lang.RuntimeException: This operation requires resolving
> level SIGNATURES but com.google.gwt.core.client.GWT is at resolving level
> DANGLING
> If you are extending Soot, try to add the following call before calling
> soot.Main.main(..):
> Scene.v().addBasicClass(com.google.gwt.core.client.GWT,SIGNATURES);
> Otherwise, try whole-program mode (-w).
> ??? at soot.SootClass.checkLevel(SootClass.java:121)
> ?? (.... there are other call stack informations)
>
>
>
> I am using the original Soot, and have also tried whole-program mode (-w) ,
> but the problem still here. Here is the command-line given in Eclipse
> console (class path is too long and has been omitted):
> soot.Main --f J --w --app --d F:\prj\soot\workspace\Test2\sootOutput --cp ##
> classpath ## --keep-line-number --xml-attributes --src-prec java
> com.zkh.gwt.test2.client.Test2
>
> Anyone have some idea on this problem? Thanks.
>
>
> Kehuan
>
> _______________________________________________
> Soot-list mailing list
> Soot-list at sable.mcgill.ca
> http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
>
>

[prev in list] [next in list] [prev in thread] [next in thread]