[Soot-list] Calling 'getCallGraph()' during whole program mode

[John Dee]

That makes sense Pat, thanks for that.
But on this note, I'm looking at the example for generating a call graph in the soot survivor's guide and it comprises:
PackManager.v().getPack("wjtp").add(new Transform("wjtp.myTrans", new SceneTransformer() {
Could you explain to me here, what the "wjtp.myTrans" argument is to the Transform object in the code snippet above?
I can't find an answer to this.
Thanks indeed                                            
> Date: Fri, 22 Jul 2011 09:30:59 -0400
> From: plam at sable.mcgill.ca
> To: soot-list at sable.mcgill.ca
> Subject: Re: [Soot-list] Calling 'getCallGraph()' during whole program mode
> 
> On 22/07/11 08:04 AM, John Dee wrote:
> > Hi there. I was looking for clarification on call graph generation. I
> > will be using Soot
> > in my M.Sc. dissertation and will need to elucidate something so that my
> > write-up makes
> > sense.
> >
> > I was reading the soot survivor's guide and on page 19, is a diagram of
> > the additional phases
> > in Soot when you put Soot into 'whole program' mode. I see that after
> > the 'jb' pack runs for
> > each method, the next pack to run is the 'cg' pack, which generates call
> > graphs and this information
> > is available to all of Soot via the 'Scene' class. My question is this:
> >
> > Once the cg pack has run, is the information generated from this pack
> > only available via a
> > scene transformer, using 'wjtp'?
> 
> The call graph, once computed, is generally available, e.g. to jtp; it 
> runs after cg and wjtp. wjtp will always run if you're creating a call 
> graph, though.
> 
> pat
> 
> _______________________________________________
> 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/20110722/4a6006e7/attachment-0001.html