[Soot-list] Interprocedural Call Graph

Eric Bodden bodden at st.informatik.tu-darmstadt.de
Wed Jul 20 17:59:33 EDT 2011


Hi John.

Interprocedural actually means that it's on the whole program. Soot
will build the graph for the whole program reachable from its main
method, including all calls to the Java runtime library. But yes, it
may take a minute or two to build.

Eric

On 20 July 2011 17:57, John Dee <jdsoot at hotmail.com> wrote:
> Hi there.
> I read in the Soot guide that to perform interprocedural analysis, you need
> to put Soot into 'whole program' mode.
> Is it possible to build a Call Graph that is not just interprocedural, but
> spans across classes? My first thoughts tell me
> this is not possible as it would be too resource intensive and would
> traverse far too many classes. Would I be right
> in saying that I would build my Call Graphs selectively for different
> methods in different classes as required, as an
> alternative approach?
> Thanks indeed for you help,
> Regards
> JD
> _______________________________________________
> Soot-list mailing list
> Soot-list at sable.mcgill.ca
> http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
>
>



-- 
Dr. Eric Bodden, http://bodden.de/
Principal Investigator in Secure Services at CASED
Coordinator of the CASED Advisory Board of Study Affairs
PostDoc at Software Technology Group, Technische Universität Darmstadt
Tel: +49 6151 16-5478    Fax: +49 6151 16-5410
Mailing Address: S2|02 A209, Hochschulstraße 10, 64289 Darmstadt


More information about the Soot-list mailing list