Comments for Eric Bodden

Comment on First steps using Soot 2.3.0 as a command-line tool by eric

eric — Wed, 10 Mar 2010 06:53:51 +0000

Fadi I have to say that your comment offends dozens of people who have been working hard on Soot and for free for many years but I will publish it anyway. By now we believe that Soot is well documented and we have a very active mailing list on which people would usually help you within minutes in case you get stuck. If you don’t ask for help then this really is your own fault. But I believe that it’s unfair to complain in this case. What problems did you encounter? Did you read our documentation? Soot certainly seems to work for hundreds of other users.

Having said that you really cannot compare BCEL to Soot. If you are fine with using BCEL then you probably would not have wanted to use Soot in the first place as BCEL is not a program-analysis framework but merely a low-level transformation framework. BCEL is great at what it does but it fulfills a purpose much different from Soot. Try doing a whole-program pointer analysis with BCEL, that should keep you busy for at least a year. With Soot it will take a minute to set one up.

Comment on Arithmetic Coding by Eric

Eric — Wed, 10 Mar 2010 06:48:43 +0000

Andrew you probably should be using some floating-point values at this point but that may require more changes to the code than just changing the data type.

Comment on First steps using Soot 2.3.0 as a command-line tool by Fadi

Fadi — Tue, 09 Mar 2010 22:47:00 +0000

Processing a bytecode by a library BCEL is way much better and easier than using Soot. At least it work. I spent 3 days (or should I say wasted) to make Soot run without complaing everytime but I was out of luck. My advice, guys dont use it!

Comment on Arithmetic Coding by Andrew

Andrew — Tue, 09 Mar 2010 21:37:41 +0000

Eric, what if my integer intervals are *really* large, say the low and high of the first symbol happens to be [19′000′000, 54′000′0000), what data types should I use? I attempt to use unsigned long, but the program enters an infinite loop when attempting E-scaling… Any suggestion?

Comment on Implementing an intra-procedural data-flow analysis in Soot by Cristina

Cristina — Sun, 07 Mar 2010 15:46:28 +0000

In code it show how to run in cmd:
if (args.length == 0) {
System.err.println(
“Usage: java -Xmx900m ADiJaCDriver -d ADiJaCDriver_output -f [grimple|class] -w -p cg off -p jb use-original-names:true -via-grimp [soot-options] classname”);
System.exit(0);
}
But I ignored this line because I run from eclipse.
p.s. If you want I write this in other place beacause I fill your blog with my questions, it’s ok for me :)

Comment on Implementing an intra-procedural data-flow analysis in Soot by Cristina

Cristina — Sun, 07 Mar 2010 15:38:19 +0000

Pack wjtp = PackManager.v().getPack(“wjtp”);
wjtp.add(new Transform(“wjtp.ad”, new ADiJaCForwardSceneInstrumenter()));
Pack jtp = PackManager.v().getPack(“jtp”);
jtp.add(new Transform(“jtp.ad”, new ADiJaCForwardBodyInstrumenter()));
soot.Main.main(args);

where ADiJaCForwardSceneInstrumenter() and ADiJaCForwardBodyInstrumenter() are implemented in other files. It’s a project partially implemented by others and I’ll have to continue the work.

Comment on Implementing an intra-procedural data-flow analysis in Soot by eric

eric — Sun, 07 Mar 2010 13:36:03 +0000

Hmm, sounds odd. I don’t see what could be wrong. What does your driver class look like?

Comment on Implementing an intra-procedural data-flow analysis in Soot by Cristina

Cristina — Sun, 07 Mar 2010 11:08:05 +0000

You’re right. I added Test.class in classpath of test2 Project( with add external class folder) but I receive the same error… I checked the command console from eclipse and it seems ok. It added:

/F:/Documents%20and%20Settings/Administrator/workspace/functie/bin/; -> that contains Test.class

When I run the project, I right click on Test.java , Soot->Process Corresponding Class File-> Run Soot… ( I tried also Process Source File) and I set the main class to my class: ADiJaCDriver and the name of the project to my project: test2.

Comment on Implementing an intra-procedural data-flow analysis in Soot by eric

eric — Sun, 07 Mar 2010 09:21:06 +0000

Hi Cristina. Soot cannot find class Test, which is not surprising because it’s neither in soot, jasmin nor polyglot. Where is the class Test located? You need to include that location on Soot’s classpath…

Comment on Implementing an intra-procedural data-flow analysis in Soot by Cristina

Cristina — Sat, 06 Mar 2010 19:11:09 +0000

Hello Eric,

I did it like you wrote here but I receive the errors:
ava.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at ca.mcgill.sable.soot.launching.SootThread.run(SootThread.java:138)
Caused by: java.lang.RuntimeException: couldn’t find class: Test (is your soot-class-path set properly?)
at soot.SootResolver.bringToHierarchy(SootResolver.java:174)
at soot.SootResolver.bringToSignatures(SootResolver.java:209)
at soot.SootResolver.processResolveWorklist(SootResolver.java:139)
at soot.SootResolver.resolveClass(SootResolver.java:124)
at soot.Scene.loadClass(Scene.java:390)
at soot.Scene.loadClassAndSupport(Scene.java:375)
at soot.Scene.loadNecessaryClass(Scene.java:929)
at soot.Scene.loadNecessaryClasses(Scene.java:943)
at soot.Main.run(Main.java:169)
at soot.Main.main(Main.java:145)
at ADiJaCDriver.main(ADiJaCDriver.java:84)

Classpath is set to folder classes of soot, jasmin and polyglot ( with Add external classes). Where was I wrong? Can you tell me, please?