Community
Participate
Working Groups
If the debug view is hidden, the variable view is not refreshed when a breakpoint is hit. That should be a consequence of the bug 27092.
Any steps to reproduce? It is, of course, working for me. This could also be related to bug 30971.
build 200302060800 linux-GTK 1. Create the following compilation unit: public class BonjourLeMonde { public static void main(String[] args) { System.out.println("Hello, World !!"); // <---- breakpoint here } } 2. Hide the debug view. 3. Launch the program as a java application. The program stops to the breakpoint. In the editor, the line where the program is stopped is selected, the stack frame indicator (blue arrow) is displayed in the ruler. The variables view stays empty. I did some other tests, if the debug view is closed during a debug session, the stack frame indicator is no more updated.
There are no variables to display - it is a static method with no locals (no this, no members).
There is something to display, if I un-hide the debug view, the stack frame become selected and "args" is added to the variable view.
Oh yeah (args). This is likely a problem with selection change events not being fired from the debug view when it is not visible.
we need to fix this (as well as the other problems with step keys and source lookup not working while the debug view is hidden).
Fixed. We had "disabled" the debug view when it was hidden. We need to process all events the same whether hidden or not - the debug view event handling is complex and required for source update/variable updates/etc. See changes in LaunchViewEventHandler.
Please verify, Jared.
*** Bug 30463 has been marked as a duplicate of this bug. ***
Verified.
*** Bug 32019 has been marked as a duplicate of this bug. ***