[Soot-list] Tracking public static final fields

Eric Bodden eric.bodden at mail.mcgill.ca
Fri Feb 16 17:31:56 EST 2007


Hmm, could it be that there is an appropriate Tag attached to your "0" value?

I am not sure why this behaviour changed at all, though...

Eric

On 2/16/07, oksana at ksu.edu <oksana at ksu.edu> wrote:
> Hello dear sooters,
> I would like to track public static final fields, e.g., if I have
>
> int i = Scrollbar.HORIZONTAL; //where Scrollbar.HORIZONTAL = 0
>
> I would like Jimple that looks like
>
> i = <java.awt.Scrollbar: int HORIZONTAL>;
>
> In the past, I have used Java-to-Jimple front end of soot and it happily
> preserved references to public static final fields. I recently updated
> to the latest version of soot and even Java-to-Jimple transformation
> seems to produce optimized code, where references to public static
> final fields are replaced with their const values, i.e.,
>
> i = 0;
>
> Here is the question: are there some options in soot to avoid such
> optimization or, given that optimization occured, is there some way to
> still recover references to public static final fields?
>
> Thank you,
> Oksana.
> _______________________________________________
> Soot-list mailing list
> Soot-list at sable.mcgill.ca
> http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
>


-- 
Eric Bodden
Sable Research Group
McGill University, Montréal, Canada


More information about the Soot-list mailing list