Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 140478

Summary: Debug problems with 3.2RC3
Product: [Eclipse Project] JDT Reporter: Genady Beryozkin <eclipse>
Component: DebugAssignee: JDT-Debug-Inbox <jdt-debug-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P3    
Version: 3.2   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Genady Beryozkin CLA 2006-05-06 14:36:56 EDT 
There are some serious problems with debugging unresolved in 3.2RC3.

First, sometimes I place a breakpoint and it is not being hit. I have a println() statement that executes (I see the output), but when I set a breakpoint at that line, nothing happens. Other breakpoints that I have set earlier are being hit. Restarting the debug session solved it.

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.
After a thread is suspended for a while (breakpoint) the debug view decides to scroll itself to the top, and the variables view becomes empty. I have to scroll down again to see the variables.

It is very hard to debug anything this way :(
Comment 1 Darin Wright CLA 2006-05-07 23:10:44 EDT 
There are 3 seperate problems in this bug report. The problems should really be separated into different bug reports so we can properly prioritize the problems and get test cases for them during RC4.
Comment 2 Darin Wright CLA 2006-05-08 09:31:08 EDT 
Created 3 new bug reports: bug 140558, bug 140559, and bug 140561.

*** This bug has been marked as a duplicate of 140558 ***