From: "Maciej W. Rozycki" <macro@mips.com>
To: Pedro Alves <palves@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
<gdb-patches@sourceware.org>,
"Maciej W. Rozycki" <macro@linux-mips.org>, <tom@tromey.com>,
<simon.marchi@ericsson.com>
Subject: Re: GDB 8.1 release -- 2018-01-08 update
Date: Mon, 08 Jan 2018 17:00:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1801081638060.20647@tp.orcam.me.uk> (raw)
In-Reply-To: <77539a17-7418-86ac-09b0-bb68650a610d@redhat.com>
On Mon, 8 Jan 2018, Pedro Alves wrote:
> > GDB uses the special thread ID 0, standing for `any', which older
> > `gdbserver' versions do not recognise. It does not verify beforehand
> > whether `gdbserver' supports this request and does not handle an error
> > reply gracefully. Consequently an error reply to a `Hg0' packet issued
> > causes GDB to lose track of what is going on, making it impossible to
> > continue with the debug session. This happens with all sessions in the
> > initial connection handshake, making the combination of new GDB and old
> > `gdbserver' unusable.
>
> I'm looking at this. I can reproduce it on x86-64 using a gdbserver
> from 2007 (git hash "f8b73d13b7ca^", the same revision Maciej's
> gdbserver is built from). I confirm that 5cd63fda035d somehow
> introduces the regression. No idea why yet.
Great, thanks!
Maciej
next prev parent reply other threads:[~2018-01-08 17:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 7:49 Joel Brobecker
2018-01-08 9:55 ` Maciej W. Rozycki
2018-01-08 16:35 ` Pedro Alves
2018-01-08 17:00 ` Maciej W. Rozycki [this message]
2018-01-09 1:28 ` [PATCH] Fix backwards compatibility with old GDBservers (PR remote/22597) (Re: GDB 8.1 release -- 2018-01-08 update) Pedro Alves
2018-01-10 11:18 ` Maciej W. Rozycki
2018-01-11 0:36 ` Pedro Alves
2018-01-08 15:50 ` GDB 8.1 release -- 2018-01-08 update Simon Marchi
2018-01-08 15:53 ` Tom Tromey
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=alpine.DEB.2.00.1801081638060.20647@tp.orcam.me.uk \
--to=macro@mips.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=macro@linux-mips.org \
--cc=palves@redhat.com \
--cc=simon.marchi@ericsson.com \
--cc=tom@tromey.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