From: Eli Zaretskii <eliz@gnu.org>
To: David Taylor <dtaylor@emc.com>
Cc: gdb-patches@sourceware.org
Subject: Re: gdb.texinfo patch
Date: Thu, 15 May 2014 17:40:00 -0000 [thread overview]
Message-ID: <83y4y3lz2z.fsf@gnu.org> (raw)
In-Reply-To: <10463.1400167510@usendtaylorx2l>
> 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).
next prev parent reply other threads:[~2014-05-15 17:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 15:25 David Taylor
2014-05-15 15:33 ` Luis Machado
2014-05-15 15:49 ` David Taylor
2014-05-15 15:53 ` Luis Machado
2014-05-15 17:40 ` Eli Zaretskii [this message]
2014-05-15 17:56 ` David Taylor
2014-05-17 7:32 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y4y3lz2z.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dtaylor@emc.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox