[Soot-list] Local variable scopes in Jimple

[Marc-Andre Laverdiere-Papineau]

Hello,

My gut feeling is 'no', because Jimple forces you to declare all your 
variables at the start of a method. They may be initialized anywhere, 
but the declaration makes their scope to be whole-method, sort of.

Of course, live variables analysis should do the trick (but double-check 
in your compiler book, my brain doesn't always work well early mornings)

Marc-André Laverdière-Papineau
Doctorant - PhD Candidate

On 13-03-19 02:11 AM, Rohan Padhye wrote:
> Hello,
>
> Does Soot provide any mechanism of determining when a JimpleLocal goes
> out of a scope in a JimpleBody?
>
> For example consider a method with the following lines:
>
> try {
>     // Something
> } catch(Exception e) {
>     // Handle e
> }
> // Some 100 more lines...
>
> I am performing data flow analysis on such methods and would like to
> determine that I can "kill" whatever
> information I am keeping for the local 'e' when it goes out of scope.
> Note that this is not limited to
> try-catch blocks but a general question regarding scope blocks.
>
> Thanks,
> Rohan Padhye
> _______________________________________________
> Soot-list mailing list
> Soot-list at sable.mcgill.ca
> http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
>