[Soot-list] Call graph construction, overriding methods

[Howard Branxon]

Hi,

When Soot constructs a call graph, can it put all of the parent and children
of a class into consideration?  It should check the corresponding classes of
each node for an overriding method.  For example, if I have

A.m1
{
B.m2();
}

And then we have C.m2 and D.m2 that override method m2 in B, our analysis
should consider B.m2(), C.m2(), and D.m2(), but right now it only considers
B.m2().

I am looking at the Soot source code in soot.jimple.tools.callgraph, and
have some ideas of what I could do, but was wondering if anyone else has
encountered this issue and has any relatively efficient ways to solve this.

Thanks!
Howie
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.CS.McGill.CA/pipermail/soot-list/attachments/20070913/9fd926e7/attachment.htm