Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Schimpe, Christina" <christina.schimpe@intel.com>
Cc: gdb-patches@sourceware.org, hjl.tools@gmail.com,
	keiths@redhat.com, aburgess@redhat.com
Subject: Re: [PATCH 1/2] gdb: add maintenance set/show gcore xml-target-description command
Date: Wed, 10 Jun 2026 14:43:06 +0300	[thread overview]
Message-ID: <864ijar585.fsf@gnu.org> (raw)
In-Reply-To: <SN7PR11MB7638222478180E79A0904994F91D2@SN7PR11MB7638.namprd11.prod.outlook.com> (christina.schimpe@intel.com)

> From: "Schimpe, Christina" <christina.schimpe@intel.com>
> CC: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
> 	"hjl.tools@gmail.com" <hjl.tools@gmail.com>, "keiths@redhat.com"
> 	<keiths@redhat.com>, Andrew Burgess <aburgess@redhat.com>
> Date: Tue, 9 Jun 2026 21:02:12 +0000
> 
> > If this command controls the emission of NT_GDB_TDESC note, then why its
> > name mentions a more general XML target description?  Am I right in
> > assuming that NT_GDB_TDESC is just part of the target description?
> > If so, perhaps the xml-target-description part should be renamed, or maybe
> > the NEWS text should be modified to say that the entire target description is
> > emitted as XML?
> 
> You're right. I should have been more specific.
> With the NT_GDB_TDESC note the core file contains a copy of GDB's target
> description XML.  Without this note the corefile does not contain the target
> description (see commit "gdb: write target description into core file").
> 
> Should we better write:
> 
> "With this command you can control whether or not the generate-core-file command
> emits the NT_GDB_TDESC note including a copy of GDB's target description XML."

Yes, this would be much more clear.

> > > +  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."), _("\ By default, gcore emits the note
> > > +NT_GDB_TDESC.\n\ Disabling this setting will cause gcore to no longer
> > > +emit this note."),
> > 
> > This doc string has the same issue: it say GDB will emit the XML target
> > description, but then goes on to say that NT_GDB_TDESC note is emitted.
> 
> Is it better as follows:
> "... gcore emits the NT_GDB_TDESC note including GDB's target description XML"

Yes, thanks.

  reply	other threads:[~2026-06-10 11:44 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 [this message]
2026-06-15  7:54         ` Schimpe, Christina
2026-06-18 17:31   ` Keith Seitz
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=864ijar585.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=aburgess@redhat.com \
    --cc=christina.schimpe@intel.com \
    --cc=gdb-patches@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --cc=keiths@redhat.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