[Soot-list] Array def/use handling

[Bernhard Berger]

Hi,

there is a slicer implemented on top of soot called Indus (http://indus.projects.cis.ksu.edu). 

Regards,
Bernhard

Am 04.06.2013 um 21:24 schrieb Marc-André Laverdière-Papineau <marc-andre.laverdiere-papineau at polymtl.ca>:

> Hello,
> 
> This is called slicing. I don't think Soot has a slicer right now.
> If you feel like implementing one, I suggest that you read a little bit
> on the topic. I personally like the TAJ paper from IBM Research.
> 
> Marc-André Laverdière-Papineau
> Doctorant - PhD Candidate
> 
> On 04/06/13 11:40 AM, Akhil Jain wrote:
>> Hi
>> 
>> Is there any way in which I can get to know what instructrions have
>> modified the array upto a specific point in the program? I tried using
>> the SimpleLocalDefs and SmartLocalDefs classes for the purpose but since
>> the array is not really stored in the form of a local variable, I
>> couldnt get much information.
>> 
>> For instance in the code:
>> 
>> int a[] = {1,0,-1}
>> if (args[0]%2==0)
>>    a[2]=factorial(a[1]);
>> else
>>    a[2]=add(a[1],a[0]);
>> System.out.println(a[2]);
>> 
>> is there any way of knowing all the statements that may have affected
>> a[2] at the point where we are printing its value?
>> 
>> Also is there any way in which this can be known along eith the path
>> taken by the execution?
>> 
>> Thanks
>> Akhil Jain
>> 
>> 
>> 
>> _______________________________________________
>> 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
> 
>