From: Daniel Jacobowitz <drow@false.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Don't query extra info about the internal main thread
Date: Thu, 24 Jul 2008 15:14:00 -0000 [thread overview]
Message-ID: <20080724151357.GA31121@caradoc.them.org> (raw)
In-Reply-To: <200807241609.35834.pedro@codesourcery.com>
On Thu, Jul 24, 2008 at 04:09:35PM +0100, Pedro Alves wrote:
> Hi,
>
> A couple of weeks ago, Dmitry Smirnov reported that GDB was trying to get
> qThreadExtraInfo out of his target and it was damaging his debug session, as
> GDB complained about a protocol error -- because the reply that came back
> was ill-formed.
>
> If the remote side doesn't have any thread support, there's no use in
> querying info about the main thread that GDB added internally. One would
> expect stubs that don't support threads to return empty to this optional
> packet, but his report showed that it's better to not rely on
> stubs behaving.
>
> Tested against gdbserver with and without --disable-packet=threads.
>
> OK?
OK.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-07-24 15:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 15:09 Pedro Alves
2008-07-24 15:14 ` Daniel Jacobowitz [this message]
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=20080724151357.GA31121@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
/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