ASM bytecode instrumentation for method entry / exit?

It looks like your code is correct, with mv.visitCode(). Javap shows the expected bytecodes. I guess your original decompiler just wasn't doing the right thing.

Thanks for the response. It turns out you are right, the decompiler is free and not the greatest indicator. Since writing this original thread, I've started using JAD decompiler, which seems reliable.

– Amir Afghani Aug 22 '09 at 6:02.

Override public void visitCode() { super.visitCode(); ... I'd use TraceClassVisitor to check exactly what was being generated.

I do have the super.visitCode() call - I just forgot to add it to the example. Good catch. Any other ideas?

When I run the instrumented code it works, it just decompiles poorly. Thanks for the response. – Amir Afghani Aug 11 '09 at 23:26 I do an mv.

VisitCode, not a super.visitCode. I dont' think thats an issue though. – Amir Afghani Aug 11 '09 at 23:27 Another discovery -- DJ Decompiler reports the correct decompiled code.

– Amir Afghani Aug 11 '09 at 23:48.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.