From: "Robert O'Callahan" <robert@ocallahan.org>
To: gdb@sourceware.org
Subject: Re: Incompatible implementat ion of 'x' packet in GDB vs LLDB
Date: Thu, 23 Jan 2025 20:12:36 +1300 [thread overview]
Message-ID: <CAOp6jLZT0Ta-C-hRC71TDjhZWg6Pyy05hEwBX0PtSzqHbGV7XQ@mail.gmail.com> (raw)
In-Reply-To: <CAOp6jLYD0g-GUsx7jhO3g8H_4pHkB6dkh51cbyDT-5yMfQwu+A@mail.gmail.com>
On Thu, 23 Jan 2025 at 08:57, Robert O'Callahan <robert@ocallahan.org>
wrote:
> GDB (client) 16.1 started sending the gdbserver 'x' packet. It follows the
> documentation [1] and expects a leading 'b' in the response [2].
> Unfortunately LLDB has supported this packet for quite a long time [3] and
> does not expect a leading 'b' in the response. We added support for this
> packet to rr last year and followed LLDB's format because it was the only
> user of the packet at that time. So GDB 16.1 doesn't work with rr. [4]
>
> I realize that compatibility between GDB and LLDB flavoured gdbserver
> protocols is not a priority for either team, but until now it has actually
> worked in practice --- rr hasn't needed a client mode switch. We can add
> one, but it will be unfortunate if GDB 16.1 and later is incompatible for
> anyone who's installed the latest rr since May 2024.
>
> Could you make a GDB 16.1 point release that removes the 'b'? AFAIK it
> serves no purpose.
>
It has been pointed out that if you want to return different error codes
then you need the 'b'. Is that the rationale?
Rob
--
Su ot deraeppa sah dna Rehtaf eht htiw saw hcihw, efil lanrete eht uoy ot
mialcorp ew dna, ti ot yfitset dna ti nees evah ew; deraeppa efil eht. Efil
fo Drow eht gninrecnoc mialcorp ew siht - dehcuot evah sdnah ruo dna ta
dekool evah ew hcihw, seye ruo htiw nees evah ew hcihw, draeh evah ew
hcihw, gninnigeb eht morf saw hcihw taht.
next prev parent reply other threads:[~2025-01-23 7:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 19:57 Robert O'Callahan
2025-01-23 7:12 ` Robert O'Callahan [this message]
2025-01-23 8:13 ` Aktemur, Tankut Baris via Gdb
2025-01-23 11:23 ` Robert O'Callahan
2025-01-23 11:39 ` Luis Machado via Gdb
2025-01-23 16:14 ` Andrew Burgess via Gdb
2025-01-23 16:33 ` Luis Machado via Gdb
2025-01-23 17:28 ` Andrew Burgess via Gdb
2025-01-23 19:38 ` Andrew Burgess via Gdb
2025-01-28 8:26 ` Pavel Labath via Gdb
2025-01-28 9:25 ` Pavel Labath via Gdb
2025-01-28 10:15 ` Luis Machado via Gdb
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=CAOp6jLZT0Ta-C-hRC71TDjhZWg6Pyy05hEwBX0PtSzqHbGV7XQ@mail.gmail.com \
--to=robert@ocallahan.org \
--cc=gdb@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