Re: [cdt-debug-dev] propose a change to CThread.handleResumedEvent()

["Mikhail Khodjaiants" <mikhailk@xxxxxxx>]

Ling,

This is a bug. The state should be set to STEPPED when the resumed event is 
fired by the backend. Please, raise a bug in Bugzilla.

Thanks,
Mikhail
----- Original Message ----- 
From: <Ling.5.Wang@xxxxxxxxx>
To: <cdt-debug-dev@xxxxxxxxxxx>
Sent: Monday, February 06, 2006 7:23 PM
Subject: [cdt-debug-dev] propose a change to CThread.handleResumedEvent()


Hi, Mikhail,

In 3.1.1 CDT, in CThread.handleResumedEvent(), there is such code:

 if ( isCurrent() && event.getType() != ICDIResumedEvent.CONTINUE ) {
     ...
     state = CDebugElementState.STEPPING;
 }

That causes a problem with our debugger which can control thread
individually.  Say, when user "Step" in one thread, a ResumedEvent is
fired from our CDI plugin for that thread (note we don't fire a
ResumedEvent for the target as some other threads are still suspended).
When CThread.handleResumedEvent() is called to handle the ResumedEvent,
it sets the state of the CThread to "STEPPING". As a result, following
suspendedEvent for the thread will be handled by
CThread.handleSuspendedEvent(), nor will the "Suspend" command be
enabled for the thread.

So I would suggest change that code to set the "state" to "STEPPED"
instead of "STEPPING". What do you think ?

Thanks.

-- Ling


_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev