[Soot-list] How does soot handle abstract classes and API/framework invocations in call graphs?

[Ishan Khot]

Thanks a lot for the answer,
However I am still interested in knowing how soot handles abstract classes
and API/framework invocations while generating the call graph?


On Tue, Jun 4, 2013 at 5:19 PM, Quentin Sabah <quentin.sabah at inria.fr>wrote:

> Hi,
> This information is computed by the chosen points-to analysis, and also
> visible in the call-graph. It is not the "exact type" of the caller, but
> the "possible types", depending on the precision of the points-to analysis.
>
> On 06/04/2013 05:15 PM, Ishan Khot wrote:
> > Hello Soot-List,
> >
> > I am interested in knowing about how soot handles abstract classes and
> > API/framework invocations while generating the call graph? Is it
> >   possible to know the exact type of the caller when a method of an
> > interface is called?
> > Thank You
> >
> >
> > _______________________________________________
> > Soot-list mailing list
> > Soot-list at sable.mcgill.ca
> > http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
>
>
> --
> Quentin Sabah, CIFRE Ph.D. student
> Grenoble University
> INRIA-SPADES                   | STMicroelectronics/AST
> Montbonnot, France             | Grenoble, France
> mailto:quentin.sabah at inria.fr  | mailto:quentin.sabah at st.com
> phone: +33 476 61 54 57        | phone: +33 476 58 44 14
> _______________________________________________
> 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/20130605/aed2502a/attachment.html