[Soot-list] Limiting the scope of Soot?

[Cheng Zhang]

Hi, Hal,

I happened to read the following post on Eric's website:

http://www.bodden.de/2010/06/04/soot-no-jdk/

I guess it may be helpful to you.

Best regards,
Cheng

On Tue, Aug 10, 2010 at 2:19 AM, Hal Hildebrand <hal.hildebrand at gmail.com>wrote:

> Things seem to be going quite well, thanks to the help I've gotten from
> this list.  In theory, I seem to have found the magic incantations to
> provide the entry points I need to make the call graph calculation work like
> I think it should.  However, now I'm running into a perhaps familiar
> problem, which is that I would like Soot to only operate on the classes I'm
> directing it too, not the entire set of JRE classes + this small set. I'm
> finding that I must set the whole program mode in order to work with the
> call graph, but I'm curious as why the entire JRE is being pulled in through
> the transformations.  I'm sure I must be doing something rather wrong.
>
> Sorry for such a naive question, but I was hoping there's some way to
> exclude what amounts to class path context for the analyzed library in
> question from the actual transformations n' such.  I certainly understand
> why Soot needs the rest of the system for context, but I'm wondering what I
> have to do to exclude it from transformations I don't want to happen any
> way...
> _______________________________________________
> Soot-list mailing list
> Soot-list at sable.mcgill.ca
> http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.cs.mcgill.ca/pipermail/soot-list/attachments/20100810/fc16fa2b/attachment.html