Community
Participate
Working Groups
Since e4, when a breakpoint is hit in Java, the Debug view selects both the thread and the stack trace element. This results in the Variables view to be empty, which is annoying. I always have to manually reselect the stack trace only to see something in the Variables view.
(In reply to comment #0) > Since e4, when a breakpoint is hit in Java, the Debug view selects both the > thread and the stack trace element. This results in the Variables view to be > empty, which is annoying. I always have to manually reselect the stack trace > only to see something in the Variables view. I don't see this using 4.3 [1] or 4.4 M1 [2] on Windows 7. Can you try with one of those builds (no additional stuff) and attach a screenshot? [1] http://download.eclipse.org/eclipse/downloads/drops4/R-4.3-201306052000/ [2] http://download.eclipse.org/eclipse/downloads/drops4/S-4.4M1-201308072000/
I am using Eclipse Juno on a Mac.
This bugs only happens sometimes, in about 30% of the cases.
(In reply to comment #3) > This bugs only happens sometimes, in about 30% of the cases. Closing then. Lots of fixes in that area have been made during Kepler. Please reopen if you see this on R4.3 or 4.4 M1.
Sorry, I always get the names confused. It is Kepler.
(In reply to comment #3) > This bugs only happens sometimes, in about 30% of the cases. Steps would help. Please make a screenshot if you see it again.
(In reply to comment #2) > I am using Eclipse Juno on a Mac. Tested on Mac + Kepler and cannot reproduce.
Created attachment 234536 [details] screenshot It happened again: Breakpoint has been hit, perspective has automatically switched to debug, thread and stack element have been selected.
Still happening (regularly) with Luna
(In reply to Jan Koehnlein from comment #9) > Still happening (regularly) with Luna "regularly" ==> steps should be possible. Please post here.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
