[Soot-list] Soot G.reset

[Steven Arzt]

Hi Eugen,

 

Where do you put the output classes? Have you made sure that they don’t accidentally end up on the Soot classpath for the second run? Are you calling G.reset() to reset Soot? Do you accidentally save some classes in fields that get preserved? Soot completely overwrites its Scene object, so whatever you get from the Scene in after the reset should not have anything to do with what you got from the Scene before – unless you still have a reference to an old class or method hanging around somewhere in your own code.

 

Best regards,

  Steven

 

Von: soot-list-bounces at CS.McGill.CA [mailto:soot-list-bounces at CS.McGill.CA] Im Auftrag von Eugen Zalinescu
Gesendet: Dienstag, 26. April 2016 09:51
An: soot-list at cs.mcgill.ca
Betreff: [Soot-list] Soot G.reset

 

Hi,

I have a similar issue to Issue#37 <https://github.com/Sable/soot/issues/37> ,  in that, when running a suite of JUnit tests, after running a first test in which some classes are transformed, and then resetting Soot and running a second test, this second test uses the transformed classes from the first test and not the untransformed ones.

Any hints on how to fix/debug this?

Thanks,

Eugen

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://mailman.CS.McGill.CA/pipermail/soot-list/attachments/20160426/f438c08a/attachment.html