GRECLIPSE

Enhanced debugger variables view support for closures

Details

  • Number of attachments :
    2

Description

In the following script, staticField, instanceField and localVariable should be visible in the debugger's variables view if a break point is positioned inside closure

new Type().method()

class Type {
    static staticField = 1
    
    def instanceField = 2

    def method() {
        def localVariable = 3

        def closure = { 
            println staticField 
            println instanceField 
            println localVariable 
        }

        closure()
    }
}

I realize this might be very difficult or impossible to do while reusing the existing JDT code but it is definitely something that will add tremendous value as closures are at the core of most things groovy. This is one of the biggest complaints I hear about using the debugger with groovy.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrew Eisenberg added a comment -

Use this to see static variables. I usually keep it off when debugging with groovy since it creates so many synthetic statics that appear, but add no value.

Show
Andrew Eisenberg added a comment - Use this to see static variables. I usually keep it off when debugging with groovy since it creates so many synthetic statics that appear, but add no value.
Hide
Permalink
Andrew Eisenberg added a comment -

I have no problem finding these variables in the variables view. Maybe it's a little confusing that you have to look inside the delegate field to find instance field.

Show
Andrew Eisenberg added a comment - I have no problem finding these variables in the variables view. Maybe it's a little confusing that you have to look inside the delegate field to find instance field.
Hide
Permalink
Andrew Eisenberg added a comment -

Are you seeing something different?

Also, I don't know if you are aware, but STS allows the use of the expressions and display views for evaluating groovy code (using groovy syntax).

Show
Andrew Eisenberg added a comment - Are you seeing something different? Also, I don't know if you are aware, but STS allows the use of the expressions and display views for evaluating groovy code (using groovy syntax).
Hide
Permalink
Bob Tiernay added a comment -

Okay, user error

But, I did notice some groovy internals in there (static variables callsites, etc.). Is it possible to filter those out? Also, is it possible to get targets of the {{Reference}}s instead of the references themselves?

Show
Bob Tiernay added a comment - Okay, user error But, I did notice some groovy internals in there (static variables callsites, etc.). Is it possible to filter those out? Also, is it possible to get targets of the {{Reference}}s instead of the references themselves?
Hide
Permalink
Andrew Eisenberg added a comment -

In the Variables view, there is a drop-down in the upper right corner. In there, you can choose the things that are filtered. I think this is sufficient. If not, please raise a new bug and describe what is still visible that you think should not be.

Show
Andrew Eisenberg added a comment - In the Variables view, there is a drop-down in the upper right corner. In there, you can choose the things that are filtered. I think this is sufficient. If not, please raise a new bug and describe what is still visible that you think should not be.
Hide
Permalink
Bob Tiernay added a comment -

So, I have been thinking about this issue a little bit. Is it possible to make delegate fields / variables directly available in the variables view when the current stack frame is the closure body? It is very disruptive to have to open the delegate variable and search for these. This would greatly aid in developer debugging productivity due to the ubiquitous nature of closures.

Show
Bob Tiernay added a comment - So, I have been thinking about this issue a little bit. Is it possible to make delegate fields / variables directly available in the variables view when the current stack frame is the closure body? It is very disruptive to have to open the delegate variable and search for these. This would greatly aid in developer debugging productivity due to the ubiquitous nature of closures.

People

  • Assignee:
    Andrew Eisenberg
    Reporter:
    Bob Tiernay
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: