[Soot-list] Retaining debug information through Soot?

[Bodden, Eric]

Hi Nathan.

> Ah, my mistake for not mentioning I had tried that option. I know that gets me Jimple with the names intact, but Soot doesn't seem to translate that into actual Java debug information when exporting a class. Thanks for the response, though!

While this is probably true (I would need to check) this should be not too hard to implement. Essentially, Soot initially parses the attributes to generate the variable names but then the original attribute is probably not actually converted into a Tag (which is Soot's internal representation of attributes). I think all one would need to do is extend Soot to create an appropriate Tag. Then in the end, this tag would automatically be written out into a bytecode attribute again by Soot. (each Tag class implements a method that defines how the tag is converted into an attribute)

One thing to keep in mind is that you might want to create these tags in the end of Soot's computation such that the tags reflect renamings/additions etc. that Soot might have made.

If you would like to work on such an extension let me know and I can give you some more pointers.

Cheers,
Eric
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://mailman.cs.mcgill.ca/pipermail/soot-list/attachments/20131122/7682c94a/attachment.bin