[Soot-list] Another problem on Soot call graph

[Eric Bodden]

Hmmm, this indeed looks like a bug to me. 

Would you mind opening a bug report for it in our bugzilla?

Good that people actually don't code that way ;-)

Eric


> -----Original Message-----
> From: soot-list-bounces at sable.mcgill.ca [mailto:soot-list-
> bounces at sable.mcgill.ca] On Behalf Of ??
> Sent: Wednesday, December 06, 2006 2:56 AM
> To: soot-list at sable.mcgill.ca
> Subject: [Soot-list] Another problem on Soot call graph
> 
> Hi everyone,
> I've written another program to illustrate the problem of Soot
> context-insensitive call graph when
> handling threads. This time I use the Spark points-to analysis results
> to build the call graph.
> 
> For the following program, EmptyThread.main() still call
> EmptyThread.run() in the call graph, but actually
> there is no such call. And I think with the Spark points-to
information
> there should be no such call. Is is
> a bug of soot? I'm now using soot 2.2.3.
> 
> 
> public class EmptyThread extends Thread{
> public void start(){
> }
> 
> public void run(){
> }
> 
> public static void main(String[] args) {
> Thread t = new IndirectThreadStart();
> t.start();
> }
> }
> 
> 
> 
> _______________________________________________
> Soot-list mailing list
> Soot-list at sable.mcgill.ca
> http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list