From: Luis Machado <lgustavo@codesourcery.com>
To: David Taylor <dtaylor@emc.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: gdb.texinfo patch
Date: Thu, 15 May 2014 15:53:00 -0000 [thread overview]
Message-ID: <5374E2ED.6050802@codesourcery.com> (raw)
In-Reply-To: <10665.1400168921@usendtaylorx2l>
On 05/15/2014 12:48 PM, David Taylor wrote:
> Luis Machado <lgustavo@codesourcery.com> wrote:
>
>> On 05/15/2014 12:25 PM, David Taylor wrote:
>>> 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.
>
> [...]
>
>> Does GDB always want to stop the thread, even when "may-interrupt" is=20
>> set to "off"?
>
> I wasn't aware of that variable, so I don't know. It will require some
> investigation. Certainly with non-stop mode turned on and may-interrupt
> at the default value, it stops it.
>
Yeah. Unfortunately it is another one of those obscure settings. :-)
Given we have this option, it may be worth mentioning it in the piece
you are patching, just for the sake of completeness. Otherwise folks may
think GDB will always stop the threads when connecting.
It will stop most of the time anyway, since it is the default after all.
Luis
next prev parent reply other threads:[~2014-05-15 15:53 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 [this message]
2014-05-15 17:40 ` Eli Zaretskii
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=5374E2ED.6050802@codesourcery.com \
--to=lgustavo@codesourcery.com \
--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