This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA] Implement *running.
On Sunday 04 May 2008 22:38:03 Eli Zaretskii wrote:
> > From: Vladimir Prus <vladimir@codesourcery.com>
> > Date: Sun, 4 May 2008 18:37:43 +0400
> > Cc: gdb-patches@sources.redhat.com
> >
> > I've added the docs. Eli, are those OK?
>
> Thanks. Yes, it's okay, except for a couple of comments:
>
> > +@item *running,thread-id="@var{thread}"
> > +The target is now running. The @var{thread} field tells which
> > +specific thread is now running, and can be @samp{all} if all threads
> > +are running. The frontend should assume that no interaction with a
> > +running thread is possible after this notification is produced.
> > +@value{GDBN} may emit this notification several times for a given
> > +thread, and the frontend should handle this gracefully.
>
> The last sentence begs a question: why would this notification emitted
> more than once,
Because internally, gdb might resume target more than once before letting
it run freely (e.g. to step over a breakpoint), and it might be hard to
reliably suppress duplicate *running
> and what do you mean by "gracefully"? just that it
> shouldn't assume the notification is emitted only once?
Yes.
How about this wording:
The frontend should not assume that this notification is output
only once for any command. @value{GDBN} may emit this notification
several times, either for different threads, because it cannot resume
all threads together, or even for a single thread, if the thread must
be stepped though some code before letting it run freely.
- Volodya