[Soot-list] Call Graph issues and advice needed

[Bernhard Berger]

Hi,

> As for the non-static entry point stuff, I'm going to ask Bernhard to 
> elaborate on that, because he dealt with it a whole lot more than I did. 
> IIRC it was because of the this pointer.
> 
> My guess is that you could patch Spark to deal with it by using CHA to 
> resolve the this pointer whenever you have a non-static entry point. 
> After all, you don't have any extra information at that point to know 
> what you're pointing to…

a year or two ago I tried to use the entry point mechanism to get a call graph of android components. I used probe to dump and check the results of the cg construction and observed that calls where missing. AFAIR there were entry methods that called another method within the class (this.foobar()) and they were missing. Furthermore there were problems with calls on the parameters. I never debugged it but I inferred that the reason is that there is information missing on the concrete type of this and the parameters. At this point I switched to entry point generation (creating a dummy main, creating the objects and parameters and call the methods).

Regards,
Bernhard