This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: MI non-stop interface details
- From: Vladimir Prus <vladimir at codesourcery dot com>
- To: Pawel Piech <pawel dot piech at windriver dot com>
- Cc: Marc Khouzam <marc dot khouzam at ericsson dot com>, Pedro Alves <pedro at codesourcery dot com>, gdb at sourceware dot org
- Date: Fri, 2 May 2008 21:35:38 +0400
- Subject: Re: MI non-stop interface details
- References: <6D19CA8D71C89C43A057926FE0D4ADAA042910AB@ecamlmw720.eamcs.ericsson.se> <200805022113.13214.vladimir@codesourcery.com> <481B4FDC.4010802@windriver.com>
On Friday 02 May 2008 21:31:08 Pawel Piech wrote:
> Right now, *stopped reports the thread which hit the breakpoint. In
> all-stop mode, all threads are stopped. In non-stop mode, only that thread
> is stopped.
>
> We surely can add an extra field to indicate which threads are actually stopped,
> if this makes life easier.
>
> Thank You :-)Â It would be more helpful if the thread-id field was
> left alone and always reported the triggering thread as it does now.Â
> It would be better (more consistent and logical) if the new field
> was used to indicate whether or not the whole container changed state.
For avoidance of doubt, do you have any objections to *running using the "thread-id"
as the field name? Since this is new notification, there's no backward compatibility
issues, and there's no issue of which thread originally triggered anything.
- Volodya