78744 – Eclipse 3.1M3 broke CDT debugger

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

Bug 78744 - Eclipse 3.1M3 broke CDT debugger

Summary: Eclipse 3.1M3 broke CDT debugger

Status:	RESOLVED DUPLICATE of bug 77060

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	Debug (show other bugs)
Version:	3.1
Hardware:	PC Linux

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	Platform-Debug-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-11-16 11:47 EST by David Pickens
Modified:	2004-11-19 15:54 EST (History)
CC List:	0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description David Pickens

2004-11-16 11:47:35 EST

The new deferred tree content provider that was recently implemented in
"DebugViewContentProvider" causes the debug launch view of CDT to so misbehave
as to render it useless.

At each step operation, the thread/stackframe tree collapses and loses focus --
causing the debug tool bar to be disabled.

I have CDT 2.0.2 installed.

Note: please do not dismiss this as a CDT bug. I traced through the debug events
of CDT and the DebugViewContentProvider seems to be failing because it can't
handle both a thread-suspend event and a target-suspend event in succession and
keep the selected stackframe showing between steps.

Comment 1 Darin Wright

2004-11-16 12:27:28 EST

Looking at the Java debugger, it fires two suspend events as well (when a 
breakpoint is configured to suspend the VM) - one for the target and one for 
the thread, in that order, which works OK. Noted that when I reversed the 
event order, the described problem occurrs.

Comment 2 Darin Wright

2004-11-19 15:54:25 EST

This is the same fix as in bug 77060.

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