RE: RE: Preserving debug information

If you're adding new methods then ASM can't manufacture LineNumberTable and
LocalVariableTable attributes out of thin air for you. You'll have to visit
those things just like you visit instructions for the new methods. 

If you haven't already you should look at ASMifierClassVisitor or the
bytecode outline plugin for eclipse for examples on how to call those. 

I don't have any experience with EMMA, but maybe there is a way to exclude
methods from its path so it won't complain

-----Original Message-----
From: [email protected] [mailto:[email protected]] 
Sent: Monday, August 01, 2011 1:04 PM
To: [email protected]
Subject: Re: [asm] RE: Preserving debug information


I did a 'javap -l' on the class files after instrumentation and they do show
LineNumberTable: and LocalVariableTable: So I guess the debug info is
present.
But I inject a couple of new methods as part of the instrumentation process
that do not have any LineNumberTable: and LocalVariableTable: 
The problem arises with running the EMMA code coverage tool which complains
about my ASM-instrumented class not containing full debug info. So it fails
to
work.
Any ideas on what can be done?

Thanks
Vijay

-- 
You receive this message as a subscriber of the [email protected] mailing list.
To unsubscribe: mailto:[email protected]
For general help: mailto:[email protected]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws