[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Target vs. Thread suspended
|
Ken,
Thank you. I'll take a look at it. I'm planning to write a simple test
target to emulate various suspend policies.
Mikhail
----- Original Message -----
From: "Ken Ryall" <kendev@xxxxxxx>
To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Sent: Thursday, September 01, 2005 1:33 PM
Subject: Re: [cdt-dev] Target vs. Thread suspended
Alain & Mikhail,
I created bug 108599 for this and included some proposals on how to
address
it. Let me know what you think and I can code one up and try it out.
Thanks - Ken
From: Alain Magloire <alain@xxxxxxx>
Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Date: Tue, 30 Aug 2005 17:50:23 -0400
To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Subject: RE: [cdt-dev] Target vs. Thread suspended
Behalf Of Mikhail Khodjaiants
Sent: Tuesday, August 30, 2005 5:10 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Target vs. Thread suspended
Some parts of org.eclipse.cdt.debug.core seem to think that when the
target is suspended all threads are suspended and other parts behave
as
if no thread is suspended if the target is not.
We definitely need to clean it up. Can you please identify the
situations
when the CDT behaves inconsistently and create a bug (or bugs) for
it?
I think fixing this probably involves replacing the
CDebugTarget.isSuspended checks with one of two tests: "is any
thread
suspended" and "are all thread suspended", usually the former.
Maybe, the backend should define the suspension policy.
Yes, maybe we should move this code in the GDB/MI debugger. Since
gdb's
view is to stop all threads, then the GDB/MI plugin should be the one
firing
suspended events for all threads.
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
