From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/dap: add support for opening core files
Date: Wed, 22 Apr 2026 11:20:18 -0600 [thread overview]
Message-ID: <878qaerjxp.fsf@tromey.com> (raw)
In-Reply-To: <87a4uw2xg0.fsf@redhat.com> (Andrew Burgess's message of "Tue, 21 Apr 2026 15:35:27 +0100")
Andrew> I had a follow up thought relating to this patch -- I wonder if we
Andrew> should add a custom capability, something like:
Andrew> @capability("supportsGDBAttachWithCoreFile")
Andrew> then a DAP user will know if they can load a core file in this way or
Andrew> not. Obviously, this would need some doc changes too...
Andrew> I'm not sure if we have any custom capabilities yet, I couldn't see
Andrew> anything documented, so I guess not.
There aren't any yet. The idea has come up from time to time. The DAP
spec doesn't make allowances for this but OTOH it's not totally clear if
doing this would really break any clients.
If we did add them maybe we should use some specific prefix like "__gdb".
Tom
prev parent reply other threads:[~2026-04-22 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 22:52 Andrew Burgess
2026-04-21 14:35 ` Andrew Burgess
2026-04-22 17:20 ` Tom Tromey [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=878qaerjxp.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@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