Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Guinevere Larsen <guinevere@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] gdb: introduce command "info architecture"
Date: Fri, 28 Nov 2025 09:20:29 +0000 (GMT)	[thread overview]
Message-ID: <alpine.DEB.2.21.2511280615320.36486@angie.orcam.me.uk> (raw)
In-Reply-To: <676535c1-9276-4ee0-87e8-fc9b0d7a78bb@redhat.com>

On Thu, 27 Nov 2025, Guinevere Larsen wrote:

> >   Is it the semantics documented in the manual since forever (search for it
> > and when it appeared there) that you disagree with?  I don't know what
> > `info unwinder' is about, but maybe someone got it wrong too and it should
> > be a `show' subcommand instead.
> 
> I know that this is what the manual and the help text say about "info", but
> that's not how the command has been used since at least the 1999 commit:
> 
> commit c906108c21474dfb4ed285bcc0ac6fe02cd400cc (tag: gdb-4_18-branchpoint)
> Author: Stan Shebs <shebs@codesourcery.com>
> Date:   Fri Apr 16 01:35:26 1999 +0000
> 
>     Initial creation of sourceware repository
> 
> in which the commands "info copying" and "info warranty" were added. The show
> version of these commands were only added in 2011.

 I can't help with that.  Also clearly the inconsistency has been noticed 
and fixed (with the old commands retained for backwards compatibility).  
That doesn't mean we ought to create more inconsistencies.

 NB the repo goes far beyond 1999 (refer commit 1730ec6b1848 for earlier 
history), although those older commits are often inconsistent owing to CVS 
conversion issues, and there were clear attempts to get this sorted long 
before and somehow lost in the mist of history.  E.g. commit a7d50b0adfcd, 
commit a3bb247ef0a2, commit 440d9834411b, and many more (search for "info 
warranty").  FWIW myself I've used GDB since 1994.

  Maciej

  reply	other threads:[~2025-11-28  9:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-06 19:45 [PATCH 0/2] Add warning if the native target is not supported Guinevere Larsen
2025-11-06 19:45 ` [PATCH 1/2] gdb: introduce command "info architecture" Guinevere Larsen
2025-11-06 23:24   ` Maciej W. Rozycki
2025-11-07 13:10     ` Guinevere Larsen
2025-11-07 15:51       ` Maciej W. Rozycki
2025-11-07 16:05         ` Hannes Domani
2025-11-08  2:02           ` Maciej W. Rozycki
2025-11-27 19:51         ` Guinevere Larsen
2025-11-27 20:00           ` Maciej W. Rozycki
2025-11-27 20:09             ` Guinevere Larsen
2025-11-28  9:20               ` Maciej W. Rozycki [this message]
2025-12-01 16:49                 ` Guinevere Larsen
2025-11-07  7:46   ` Eli Zaretskii
2025-11-07 13:41     ` Guinevere Larsen
2025-11-07 14:23       ` Eli Zaretskii
2025-11-08  2:25       ` Maciej W. Rozycki
2025-11-27 20:01         ` Guinevere Larsen
2025-11-28  9:20           ` Maciej W. Rozycki
2025-11-06 19:45 ` [PATCH 2/2] gdb: add warning when no native target is available Guinevere Larsen
2025-11-07  7:48   ` Eli Zaretskii
2025-11-07 13:24     ` Guinevere Larsen
2025-11-07 14:21       ` Eli Zaretskii
2025-11-27 20:15         ` Guinevere Larsen

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=alpine.DEB.2.21.2511280615320.36486@angie.orcam.me.uk \
    --to=macro@orcam.me.uk \
    --cc=gdb-patches@sourceware.org \
    --cc=guinevere@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