Community
Participate
Working Groups
From bug 140478: "Second, sometimes, when a breakpoint is hit, the debug view does not scroll to the suspended thread to show the call stack. Also when the suspended thread is not visible, the variables view is empty. I have to scroll down to the suspeded thread and only when it appears in the debug view I see the variables in the variables view."
Reported against 3.2RC3. Screen shot's or test case would be helpful. Were you debugging an Eclipse workbench? were there many threads?
I was debugging Eclipse 3.1.2 workbench. I will attach a screenshot little later when I'll be near my laptop.
The scenario is: I have two breakpoints. The program hits the first breakpoint and I press F8 to continue. Then it hits the second breakpoint and now sometimes I must manually scroll down to see the suspended thread. No other threads are suspended. After I scroll down and wait a little, it automatically scrolls up and variables disappear, F8 is inactive, etc. I'll send the screenshots by email.
See bug 138189. When a thread suspends, we expand it, which makes it visible. This causes the debug view to show the thread (bug 138189), even if another thread has focus. So, if you more than one thead suspending at once, this may be the cause. However, I have not seen the problem of the variables view being emty when this occurrs.
Do you think bug 141395 can be the reason to this bug?
Bug 141395 is Mac specific - so, no, I don't think so.
I just keep seing this behavior, sometimes even a simple "Step over" would cause it. Maybe there is some similar SWT problem on Windows...
and this one... is it still an issue in the latest 3.2.1 build? (There is another one tomorrow, July 26th).
It is still an issues with 3.2 (happened to me just a minute ago). I'm having problems with updating to new builds because of bug 122041 for which i use a local patch (which requires me to rebuild parts of pde). I'll try the new build in a couple of days.
*** Bug 149727 has been marked as a duplicate of this bug. ***
Any luck with one of the newer builds?
I don't see the problem anymore. I think I have some other problems with debug which might be related, but I'll log them separately.
Thanks for reporting back. Marking as works for me.
This should be more like "works for you" :) Do you have any idea what was the 3.2.1 change that fixed it?
I think the fix to bug 143805 will also fix this one.
