Summary: | Around advice weaving generates repeated methods | ||
---|---|---|---|
Product: | [Tools] AspectJ | Reporter: | Eduardo Cordeiro <escordeiro> |
Component: | Compiler | Assignee: | aspectj inbox <aspectj-inbox> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P5 | CC: | aclement |
Version: | 1.5.2 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | All | ||
Whiteboard: |
Description
Eduardo Cordeiro
2006-08-17 12:27:19 EDT
I forgot to mention that the javap command was run after compiling the code with ajc1.5.2, provided with AJDT 1.4 for Eclipse 3.2. worth a try getting this into 1.5.3 Decompiling the provided testcase with "javap -private -verbose BugExample" shows that the LineNumberTables are different. (In reply to comment #3) Indeed, the LineNumberTables for shadow methods are different, since they refer to different shadows. So this affects debugging, since the same instruction can't refer to several source-code lines. Can the repeated methods still be applied if line number information is not generated? (or more specifically, if debug is disabled?) unsetting the target field which is currently set for something already released |