[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-debug-dev] propose a change to CThread.handleResumedEvent()
|
Sorry, just to correct a typo. The sentence was meant to be
"...following suspendedEvent for the thread will NOT be handled by
CThread.handleSuspendedEvent()...".
> -----Original Message-----
> From: cdt-debug-dev-bounces@xxxxxxxxxxx
> [mailto:cdt-debug-dev-bounces@xxxxxxxxxxx]
> Sent: Monday, February 06, 2006 6:23 PM
> To: cdt-debug-dev@xxxxxxxxxxx
> 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
>
