From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <aburgess@redhat.com>
Cc: Luis Machado <luis.machado@arm.com>,
Stephen Brennan <stephen.s.brennan@oracle.com>,
Tom Tromey <tom@tromey.com>,
Luis Machado via Gdb <gdb@sourceware.org>,
linux-debuggers@vger.kernel.org,
Omar Sandoval <osandov@osandov.com>,
Amal Raj T <tjarlama@gmail.com>
Subject: Re: GDB Remote Protocol Extension - Linux VMCOREINFO - Request for Feedback
Date: Fri, 17 Jan 2025 15:01:43 -0700 [thread overview]
Message-ID: <87ed11umk8.fsf@tromey.com> (raw)
In-Reply-To: <87y0zaogoh.fsf@redhat.com> (Andrew Burgess's message of "Thu, 16 Jan 2025 16:40:46 +0000")
>>>>> "Andrew" == Andrew Burgess <aburgess@redhat.com> writes:
Andrew> I doubt, right now, there are many
Andrew> "custom packets" in the wild, but maybe we should consider defining
Andrew> namespaces for custom packets, to avoid future conflicts?
Right now most of the incompatible packets in the wild are from
lldbserver. They extended the protocol but didn't discuss with gdb or
send patches to the docs.
The other major incompatibility I see in the wild is custom servers that
send weird results. I've sent a workaround or two for these kinds of
things in the past.
Anyway, for a new qXfer packet, I guess I don't see much to worry about.
Hopefully people adding such things have the wisdom to pick an unusual
name.
Andrew> I've had success using packets via Python before, and not everyone is
Andrew> aware this feature is available, so I thought I'd mention it.
It didn't cross my mind but yeah this seems like a reasonable use case.
Tom
next prev parent reply other threads:[~2025-01-17 22:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8734hmtfbr.fsf@oracle.com>
2025-01-14 15:03 ` Luis Machado via Gdb
2025-01-14 17:15 ` Tom Tromey
2025-01-14 17:39 ` Stephen Brennan via Gdb
2025-01-16 10:37 ` Andrew Burgess via Gdb
2025-01-16 10:49 ` Luis Machado via Gdb
2025-01-16 16:40 ` Andrew Burgess via Gdb
2025-01-16 17:15 ` Luis Machado via Gdb
2025-01-17 22:01 ` Tom Tromey [this message]
2025-01-16 17:58 ` Stephen Brennan via Gdb
2025-01-23 1:11 ` Stephen Brennan via Gdb
2025-01-26 18:07 ` Thomas Weißschuh via Gdb
2025-01-27 18:13 ` Omar Sandoval
2025-01-27 18:42 ` Stephen Brennan via Gdb
2025-01-27 22:40 ` Thomas Weißschuh via Gdb
2025-01-28 0:19 ` Stephen Brennan via Gdb
2025-01-29 21:16 ` Thomas Weißschuh 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=87ed11umk8.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.com \
--cc=gdb@sourceware.org \
--cc=linux-debuggers@vger.kernel.org \
--cc=luis.machado@arm.com \
--cc=osandov@osandov.com \
--cc=stephen.s.brennan@oracle.com \
--cc=tjarlama@gmail.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