[Soot-list] Different Jimple output from command line and Eclipse

[Eric Bodden]

> I wonder why could this happen? Is it because that the Eclipse would run the
> program with different command line option?

There could be two reasons. First, are you actually analyzing the same
class files? Class files produced by Eclipse could be different than
those e.g. produced by javac and could cause Soot to produce different
(but equivalent) Jimple. Second (and more likely), the Eclipse plugin
uses by default an option to keep local-variable names in Jimple (you
can see it in the output). On the command line, this option is
disabled by default. Keeping local variable names means that Soot has
to apply some transformations to the Jimple code, which may explain
the difference.

Eric