Re: sootifying Java system classes

[Patrick LAM <plam@sable.mcgill.ca>]

On 12 Feb 2002, Rhodes H. F. Brown wrote:

> > I have poked through the Soot docs (including a quick skim over the
> > mailing list archive) and I cannot seem to figure out Soot's strange
> > treatment of the Java system classes (i.e. those in rt.jar).

...

> > java soot.Main --soot-classpath ./rt -d sootified --process-path ./rt
> >
> > all I get are the com.* classes. Similarily, when one specifies the
> > --app option, Soot will not process the system classes. What is going on
> > here? I assume that there is a filter at some point that excludes java.*
> > (and similar) classes. Does anyone know where this is in the Soot
> > source? Can it be circumvented? Is this a good idea?

The default behaviour of Soot is to exclude the java.*, javax.*, and sun.*
classes, so that compilation finishes in a reasonable amount of time.  If
you want to include them, try -i java. -i sun. -i javax., I think that
should work.  For the source reference, see soot.Main.initApp.

By the way, you don't actually need to untar rt.jar anymore; Patrice
checked in a change which allows us to read jar files.

pat