Re: sootifying Java system classes

[Ondrej Lhotak <olhotak@sable.mcgill.ca>]

It sounds like you are looking for the -a (--analyze-context) switch
to Soot. The drawback is that it makes Soot run for a long time.

Ondrej

On Tue, Feb 12, 2002 at 03:33:24PM -0500, Rhodes H. F. Brown wrote:
> This is another attempt at a post that did not make it through the first
> time...
> 
> On Fri, 2001-11-16 at 17:09, Rhodes H. F. Brown wrote:
> 
> > Hello all,
> > 
> > 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).
> > 
> > For example, I unjarred my rt.jar file to a local rt directory. Then I
> > did:
> > 
> > java soot.Main --soot-classpath ./rt -d sootified java.lang.String
> > 
> > This works fine. As indicated in the intro tutorial, I get a new
> > java.lang.String.class. However, if I try:
> > 
> > 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?
> 
> -- 
> Rhodes Brown
> Sable Research - McGill University
> 
> Web:    http://www.sable.mcgill.ca
> Email:  rhodesb@sable.mcgill.ca
>