see the instrumented code

[Guy Korland]

Hi Arie,
I added this thread to the forum since I think it might interest
others.
Please send such questions in the future to this forum.
1. Use -Dorg.deuce.verbose=true this will spit all the bytecodes
created be
Deuce, then you can use any dissasmbler you want, e.g. jad.
2. l1 and l2 are used by the code that generates if-else block. l1 is
the
else while l2 is the end of the else block.
It calls visitFieldInsn to load the field we wanted to read and to
load the __address field.
Guy

On Wed, Jul 8, 2009 at 8:52 PM, Arie Zilberstein
<arie.zilberst...@gmail.com
> wrote:
> Hi,
> 1. Is there a way to see the instrumented code as java code?
> I tried running the instrumented code through a java disassembler, and the
> results are very strange for some reason.
> is there a better way?
> 2. Regarding DuplicateMethod.visitFieldInsn() method, could you
> explain what's wrong on there?
> what's the l1 and l2 labels for?
> isn't it strange that you invoke super.visitFieldInsn(opcode, owner, name,
> desc); in more than one place in that method? It can be called twice in the
> same flow.
> Best,
> Arie