Community
Participate
Working Groups
build I20050330-0500 In the last few I-builds, I've noticed that often, when a breakpoint is hit soon after resuming from a previous one using F8, the stack frame at the breakpoint is not selected. The Debug view gets focus, but there is no selection. It seems that this usually happens when I had focus in the editor or the variables view, and when the next breakpoint is hit very soon after resuming.
VM: pj9n142-20040928a
Nick, is this still happening? We have not noticed it lately.
Not sure about the latest builds, but I was seeing it not too long ago. I think it should be kept open for a while longer. I'll keep a lookout for it, and let you know.
This happened to me today. I was launching with a breakpoint set that would get hit immediately. To reproduce, I just close the debug perspective and press F11. Because of a bug in the PDE I'm currently forced to use a pre-M7 build.
The selection problem when switching perspectives is a due to bug 73188. Perhaps this is a duplicate.
I also see this on gtk on N20050523. The editor does not get revealed either, I have to select the top stack frame to bring the corresponding editor to the top.
sorry, I've seen this for a while, but not with N20050523, as I see bug 96294 there.
In my case, the editor was already active when I pressed F11. So the problem is definitely not activating the editorpart, unless the ui sent extra notification for activating an already active editor.
I haven't seen this in the latest builds. I just tried again, and it worked OK, but there was some inconsistency in the impact of refreshing the Debug views. About half the time it did a full refresh, other times it seemed instantaneous, but it did not lose the selection. Steps: - platform-ui and prereqs from CVS - rest as external binaries - set breakpoint in ActionBarAdvisor.register(IAction) - launch IDE under Debug - hit F8 about once a second - sometimes the Debug view does a full refresh, with a noticeable flash, sometimes it needs to do very little work at all with no flash, but it updates correctly either way (e.g. look at line number for WorkbenchActionBuilder.makeActions, and action var in Variables view)
I can reproduce this every time using 0525-0100 build. Nick, which build were you using? Did you already have the perspective open?
build I20050527-0900, using pj9n142ifx-20041206 as my host VM and Sun JDK 1.4.2_01 as my target VM. I tried in both my custom perspective, and in the debug perspective (already open).
Releasing a change to RemoteTreeViewer that may fix this problem. Since I can't reproduce the problem reliably, I'm not positive it's a complete fix. Fix will be in the 8PM build today. We had a couple places in our "replace/merge" code that replaces old content with newly retrieved content from the target, without re-scheduling the "deferred selection" job. All code paths now ensure to run the deferred updates (selection/expansion).
Marking as works for me. Please re-open or file a new bug if the problem persists.
Reproducing on RC3 is trivial and the steps have been provided in comment 4.
I tried with a breakpoint on the first statement of a "main", but the perspective is still opened, the frame is selected, and source is displayed (Win XP, 3GHz P4).
Make sure you first close all editors and close the debug perspective.
Still works, after closing all editors and all perspectives (except Java).
My test case is that I'm trying to debug an SWT application that does not have the DLL on the library path. So, org.eclipse.swt.internal.Library#loadLibrary throws an exception, which is caught and the debugger attempts to display line 131 but nothing happens. If I put a breakpoint in main, it also fails to display the breakpoint. Perhaps the z-order of parts in the debug perspective is important. Have you customized the debug perspective? Mine appears to be the default.
Also works for me in a brand new workspace (no alterations to user preferences). The first time I try, I am prompted to switch to debug perspective (works, and I select "remember my decision to switch"). I then closed the debug perspective and all editors and restarted the workspace. On the next try, it also works, without prompting.
Deferred for post 3.1
works for me in 3.2
marking as works for me.
