[Soot-list] Help to soot

[Bernhard Berger]

Hi,

I'm not quite what you are trying to do. Do you want to extract the call relations from bytecode? Soot does this in the callgraph construction. It reads all instructions from the class files and converts them to Jimple (an intermediate representation). Afterwards, the call graph is constructed and can be accessed (and I think it even can be modified). There are different callgraph construction algorithms that differ in runtime, memory consumption and preciseness. 

I hope I was able to help you.

Regards,
Bernhard

Am 16.05.2013 um 17:47 schrieb GIUSEPPE RIGANO <giusepperig at hotmail.it>:

> Hello everyone, I'm a college student Italian, wanted to know if soot was for me.
> My case:
> I would make a call tree with bytecode instructions such as "callgraph" that you get by clicking on Run soot and setting "Interactive mode", however, that you can manipulate. I would like to get for each invocation of a method on my respective "call tree". I had seen the example callgraph but I do not know if it is right for me. I had difficulty in understanding how it works.
> Should I create a class that scans the bytecode and every time an instruction target is found, it visit the call tree and then reconstruct the state of the stak operands.
> 
> Thanks in advance!
> 
> Rigano Giuseppe
> _______________________________________________
> 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/20130517/b8d36370/attachment.html