Bug 512840 - Eclipse debug breakpoints not hit when using TestNG and AspectJ with load-time weaving
Summary: Eclipse debug breakpoints not hit when using TestNG and AspectJ with load-tim...
Status: NEW
Alias: None
Product: AspectJ
Classification: Tools
Component: LTWeaving (show other bugs)
Version: 1.8.9   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-28 15:51 EST by Tim Boemker CLA
Modified: 2017-02-28 15:53 EST (History)
1 user (show)

See Also:

Attachments
Eclipse project demonstrating the bug (1.82 MB, application/octet-stream)
2017-02-28 15:51 EST, Tim Boemker CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Boemker CLA 2017-02-28 15:51:38 EST 
Created attachment 267038 [details]
Eclipse project demonstrating the bug

When AspectJ with load-time weaving and TestNG are used together, Eclipse breakpoints are skipped or mapped incorrectly.

In the attached project, please set breakpoints at TestAdvice:9 and IsAdvised:5.  Debug using the test-aj launch.  When the breakpoint at TestAdvice:9 is reached, Step Into.  The current line at that point should be IsAdvised:5, which is the call to goo(), but the current line is actually IsAdvised:6; the call to goo() was skipped.

I am running the attached project in Eclipse Mars with AspectJ installed from http://download.eclipse.org/tools/ajdt/46/dev/update.  This used to work with Eclipse Kepler; I think that it's been broken since Luna.