[Soot-list] About reaching definitions analysis in soot

[Steven Arzt]

Hi Steven,

 

Soot implements an interprocedural reaching definitions analysis based on
the Heros IFDS/IDE framework. Actually, this is one of the example problem
implementations we ship with Soot to show how Heros is used with Soot. You
can find the implementation in class
”soot.jimple.toolkits.ide.exampleproblems. IFDSReachingDefinitions”. What
you need to do to use it, is fairly simple: Create an instance of the
IFDSSolver class, give it an instance of the problem class above, call
“solve” and fetch the results using “resultsAt”.

 

Best regards,

  Steven

 

PS: It’s funny to  reply to someone who has the same first name ^^

 

 

M.Sc. M.Sc. Steven Arzt

Secure Software Engineering Group (SSE)

European Center for Security and Privacy by Design (EC SPRIDE) 

Mornewegstraße 32

D-64293 Darmstadt

Phone: +49 61 51 16-75426

Fax: +49 61 51 16-72118

eMail:  <mailto:steven.arzt at ec-spride.de> steven.arzt at ec-spride.de

Web:  <http://sse.ec-spride.de/> http://sse.ec-spride.de

 

 

 

Von: soot-list-bounces at sable.mcgill.ca
[mailto:soot-list-bounces at sable.mcgill.ca] Im Auftrag von Steven Lee
Gesendet: Donnerstag, 27. März 2014 08:00
An: Soot Group
Betreff: [Soot-list] About reaching definitions analysis in soot

 

Hello everyone, would anyone can help me with some questions?

1.      How to do reaching definitions analysis with soot? Does soot already
implement it, or I need to implement it myself with the data-flow framework?


2.      I want to do this analysis for some java source code and then mark
each variables potential definitions, but I find that soot does its main
analysis on the corresponding jimple file. So my question is: if I finished
the analysis on a jimple file, how to I transform these results to my java
source file?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.cs.mcgill.ca/pipermail/soot-list/attachments/20140327/b767d58c/attachment.html