You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Paul King (JIRA)" <ji...@apache.org> on 2018/12/16 03:35:00 UTC

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

     [ https://issues.apache.org/jira/browse/GROOVY-4063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul King resolved GROOVY-4063.
-------------------------------
    Resolution: Duplicate

This seems to work with 2.4.16 and 2.5.5-SNAPSHOT, I presume it was fixed by GROOVY-8742.

> Debugger Step Into doesn't work in Groovy-compiled classes when stepping filters are applied
> --------------------------------------------------------------------------------------------
>
>                 Key: GROOVY-4063
>                 URL: https://issues.apache.org/jira/browse/GROOVY-4063
>             Project: Groovy
>          Issue Type: Bug
>          Components: class generator
>    Affects Versions: 1.6.7, 1.7.0
>            Reporter: Peter Gromov
>            Priority: Major
>         Attachments: debug-test.tar.gz
>
>
> 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.*
> {code}
> class Some {
> 	static void meth() {
> 		println "Method is called."
> 	}
> 	public static void main(String[] args) {
> 		meth()		// breakpoint here
> 	}
> }
> {code}
> 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)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)