From: Keith Seitz <keiths@redhat.com>
To: Christina Schimpe <christina.schimpe@intel.com>,
gdb-patches@sourceware.org
Cc: hjl.tools@gmail.com
Subject: Re: [PATCH 1/2] gdb: add maintenance set/show gcore xml-target-description command
Date: Thu, 18 Jun 2026 10:31:03 -0700 [thread overview]
Message-ID: <39064284-dcaa-45ee-a504-1475803f66eb@redhat.com> (raw)
In-Reply-To: <20260602111122.3187712-2-christina.schimpe@intel.com>
Hi,
On 6/2/26 4:11 AM, Christina Schimpe wrote:
> From: Felix Willgerodt <felix.willgerodt@intel.com>
>
> This command will allow to enable/disable creating the NT_GDB_TDESC note
> in corefiles. While GDB writes and reads this node, there aren't really many
> other pieces of software that create this node (e.g. the Linux kernel doesn't).
> To be able to test the code path in GDB that is used when NT_GDB_TDESC is not
> there, add a maintenance command which tests can use to test both cases.
Thank you for working on supporting Intel APX. I just have a tiny nit
or two on this patch which otherwise LGTM.
> diff --git a/gdb/gcore.c b/gdb/gcore.c
> index e50115370c7..03876969ae9 100644
> --- a/gdb/gcore.c
> +++ b/gdb/gcore.c
> @@ -928,4 +947,25 @@ Usage: generate-core-file [FILENAME]\n\
> Argument is optional filename. Default filename is 'core.PROCESS_ID'."));
>
> add_com_alias ("gcore", generate_core_file_cmd, class_files, 1);
> +
> + add_basic_prefix_cmd ("gcore", class_maintenance,
> + _("gcore maintenance commands."),
> + &maint_gcore_cmdlist, 0, &maintenancelist);
> +
> + add_setshow_prefix_cmd ("gcore", class_maintenance,
> + _("Set gcore specific variables."),
> + _("Show gcore specific variables."),
> + &maint_gcore_set_cmdlist, &maint_gcore_show_cmdlist,
> + &maintenance_set_cmdlist, &maintenance_show_cmdlist);
> +
> + add_setshow_boolean_cmd ("xml-target-description", class_obscure,
> + &maint_gcore_emit_xml_tdesc, _("\
> +Set whether gcore emits a xml-target-description."), _("\
> +Show whether gore emits a xml-target-description."), _("\
^^^^
In case it hasn't been mentioned, this should be "gcore".
Super nit (sorry): please use "an xml-target-description".
> +By default, gcore emits the note NT_GDB_TDESC.\n\
> +Disabling this setting will cause gcore to no longer emit this note."),
> + nullptr,
> + show_gcore_xml_target_description,
> + &maint_gcore_set_cmdlist,
> + &maint_gcore_show_cmdlist);
> }
Reviewed-By: Keith Seitz <keiths@redhat.com>
Keith
next prev parent reply other threads:[~2026-06-18 17:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 11:11 [PATCH 0/2] Add Intel APX support Christina Schimpe
2026-06-02 11:11 ` [PATCH 1/2] gdb: add maintenance set/show gcore xml-target-description command Christina Schimpe
2026-06-02 12:22 ` Eli Zaretskii
2026-06-09 21:02 ` Schimpe, Christina
2026-06-10 11:43 ` Eli Zaretskii
2026-06-15 7:54 ` Schimpe, Christina
2026-06-18 17:31 ` Keith Seitz [this message]
2026-07-07 17:07 ` Schimpe, Christina
2026-07-10 11:57 ` Schimpe, Christina
2026-06-02 11:11 ` [PATCH 2/2] gdb, gdbserver: Add Intel APX register support Christina Schimpe
2026-06-02 12:25 ` Eli Zaretskii
2026-06-18 17:33 ` Keith Seitz
2026-07-07 17:15 ` Schimpe, Christina
2026-07-07 17:53 ` Keith Seitz
2026-07-07 17:15 ` Schimpe, Christina
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=39064284-dcaa-45ee-a504-1475803f66eb@redhat.com \
--to=keiths@redhat.com \
--cc=christina.schimpe@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@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