[GROOVY-4063] Debugger Step Into doesn't work in Groovy-compiled classes when stepping filters are applied

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.6.7, 1.7.0
• Component/s: class generator
• Assignee: Unassigned
• Reporter: Peter Gromov
• Created: 16/Feb/10 09:12
• Updated: 20/May/19 07:31
• Resolved: 16/Dec/18 03:34

Description

Reproduced in IntelliJ IDEA 9, GroovyEclipse 2.0 and JSWAT 4.5, therefore the problem is probably in Groovy itself.

Stepping class exclusion filters are set to ignore everything from Java and Groovy internals: groovy.,org.codehaus.groovy.,java.,sun.,org.apache.*

class Some {
	static void meth() {
		println "Method is called."
	}

	public static void main(String[] args) {
		meth()		// breakpoint here
	}
}

Run to the breakpoint in 'main' method. 'Step into'. There's a very long pause (presumably JVM applies the filters to all the underlying groovy internals), the message is printed and the program exits. Breakpoint is not hit.

Now put the breakpoint to the 'println' line in 'meth' and repeat stepping into. This time the debugger stops at it.

Stepping worked in earlier Groovy versions (e.g. 1.5) and stopped in 1.6. Therefore I suspect it to be somehow mystically related to class generation (or the libraries used, whatever)

Issue Links

• duplicates: GROOVY-8742 Line number information for method is confusing debugger
• relates to: GROOVY-9076 Debugger Step Into doesn't work in Groovy-compiled classes