This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: gdb.texinfo patch
- From: Eli Zaretskii <eliz at gnu dot org>
- To: David Taylor <dtaylor at emc dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Thu, 15 May 2014 20:40:52 +0300
- Subject: Re: gdb.texinfo patch
- Authentication-results: sourceware.org; auth=none
- References: <10463 dot 1400167510 at usendtaylorx2l>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: David Taylor <dtaylor@emc.com>
> Date: Thu, 15 May 2014 11:25:10 -0400
>
> In writing a new stub (to replace our old stub), I have discovered what
> I believe to be the rule for how GDB chooses which thread to stop during
> the initial connection. Knowing this sooner would have saved my some
> grief. Hoping to help the next person avoid that same grief, here's a
> patch (as a unified diff against gdb/doc/gdb.texinfo of GDB 7.7) to
> document it.
Thanks.
> +@emph{Note: @value{GDBN} will send the qfThreadInfo query during the
^^^^^^^^^^^^
The packet name should be in @code.
> +initial connection with the remote target. And the very first thread ID
> +mentioned in the reply will be stopped by @value{GDBN} in a subsequent
> +message. Therefore the stub should ensure that the first thread ID in
Better make the second sentence part of the first (as in "..., and the
very first thread ...").
> +the qfThreadInfo reply is suitable for being stopped by @value{GDBN}.}
^^^^^^^^^^^^
@code
Otherwise, fine with me, assuming the contents is correct (I don't
know enough to say).