This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: gdb.texinfo patch
- From: David Taylor <dtaylor at emc dot com>
- To: "lgustavo at codesourcery dot com" <lgustavo at codesourcery dot com>
- Cc: "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Thu, 15 May 2014 11:48:41 -0400
- Subject: Re: gdb.texinfo patch
- Authentication-results: sourceware.org; auth=none
- References: <10463 dot 1400167510 at usendtaylorx2l> <5374DE29 dot 3010606 at codesourcery dot com>
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.