From: Tom Tromey <tom@tromey.com>
To: Luis Machado via Gdb <gdb@sourceware.org>
Cc: Stephen Brennan <stephen.s.brennan@oracle.com>,
Luis Machado <luis.machado@arm.com>,
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: Tue, 14 Jan 2025 10:15:16 -0700 [thread overview]
Message-ID: <87plkpqpuj.fsf@tromey.com> (raw)
In-Reply-To: <5e1c692b-b103-4c47-8cc3-d8ce487d98e1@arm.com> (Luis Machado via Gdb's message of "Tue, 14 Jan 2025 15:03:16 +0000")
>>>>> Luis Machado via Gdb <gdb@sourceware.org> writes:
>> To sum up, my specific questions are:
>>
>> 1. What is the maximum protocol packet size, if any?
> It is hardcoded by gdb, but the remote can also specify that, but...
>> 2. Would this functionality be better implemented in a single "q
>> linux.vmcoreinfo" packet, or as a "qXfer" packet?
> ... we have packets like qXfer that can handle multi-part transfers. So the
> packet size is not a critical concern anymore, and it is best to use this
> newer mechanism, if the usage fits the packet structure.
Agreed, qXfer is the way to go.
If you're adding a new object type, a patch to the manual would be good.
Tom
next prev parent reply other threads:[~2025-01-14 17:16 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 [this message]
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
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=87plkpqpuj.fsf@tromey.com \
--to=tom@tromey.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