[Soot-list] Call Graph with non-static entry points?

[Laurie Hendren]

Hi Marc-Andre,

I would have to look to see why that would be a problem,  but it may 
have to do with needing a concrete object for the receiver.     In fact, 
if your entry points are not static, doesn't some method need to create 
an object on which it calls your entry point ..

If so, then wouldn't you just have to create a dummy static method that 
creates an object and makes the call,  and then start the call graph 
algorithm at the dummy static method?

Or ... am I misunderstanding your question?

Laurie



+--------------------------------------------------------------
| Laurie Hendren --- http://www.sable.mcgill.ca/~hendren
| Associate Dean (Academic), Faculty of Science
| Professor, School of Computer Science, McGill University
| New McLAB project:  http://www.sable.mcgill.ca/mclab/
| Also: www.sable.mcgill.ca/soot  www.sable.mcgill.ca/abc
+--------------------------------------------------------------

On 10/01/2013 10:30 PM, Marc-Andre Laverdiere-Papineau wrote:
> Hello,
>
> Chatting with Bernhard yesterday, he was telling me that there are
> problems with Spark when the entry points are not static.
>
> Since my entry point detection framework is very good at detecting
> non-static things, I am wondering if that is making the framework moot.
>
> Can anyone confirm whether Spark, or call graph constructions algorithms
> in general, have an assumption concerning the type of entry points it is
> dealing with? Or should that be considered as a bug that we'll fix along
> the way?
>
> Regards,
>