[Soot-list] side-effect and exception analysis with soot

[Al]

rifk there is a throw analysis in soot.

On May 8, 2013, at 12:37 PM, Marc-André Laverdière-Papineau <marc-andre.laverdiere-papineau at polymtl.ca> wrote:

> Hello,
> 
> First, thanks for letting us know about your project!
> 
> Sorry for the late reply. I was hoping that one of the wiser folks would 
> answer, but no luck ;)
> 
> From what I can see in the code, there is a side effect analysis 
> available in the Soot code and stored in the Scene singleton. There are 
> a few other implementation at other places that I can see, like in the 
> Geometric PTA implementation. I am not seeing code for exception analysis.
> 
> My guess is that you are looking for interprocedural analysis, right? 
> Have you considered implementing that analysis in the IDE framework?
> 
> Regards,
> 
> 
> Marc-André Laverdière-Papineau
> Doctorant - PhD Candidate
> 
> On 02/05/13 02:36 PM, Martin Schäf wrote:
>> Hi there,
>> we have a tool that uses soot to translate from java bytecode to
>> boogie (https://code.google.com/p/joogie/). For that we need to know
>> for each method which global variables (StaticFields) it modifies
>> (this actually has to be transitive, but may be a worst case
>> over-approximation) .
>> It would also be great to know the InstanceFields it may write to.
>> 
>> Further we need to know which it exception might be thrown (including
>> stuff like RuntimeException), again this has to be transitive as well.
>> 
>> We have an implementation, but it is very ugly. So, I was wondering,
>> is there an elegant way in Soot to obtain side-effects and worst-case
>> exception analysis from Soot?
>> 
>> Best,
>> Martin
>> _______________________________________________
>> Soot-list mailing list
>> Soot-list at sable.mcgill.ca
>> http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
> _______________________________________________
> Soot-list mailing list
> Soot-list at sable.mcgill.ca
> http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list