From: Zander Work via Gdb <gdb@sourceware.org>
To: Guinevere Larsen <guinevere@redhat.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Question about adding a new option vs extending an existing one
Date: Thu, 30 Apr 2026 15:46:47 +0000 [thread overview]
Message-ID: <-tT8gWCj1g1GjvJRl43XWZw617t_INK4DMPtVHfOvkCNNIFLeYs2Fylz6xQLXmVXqo69m-h3iMq4yFB9WDuZCrQKeVqtRDlOGO1lAbt9AXc=@zanderwork.com> (raw)
In-Reply-To: <3ff2c828-eb48-4c5a-9862-5fc6e9be3231@redhat.com>
Cool, that makes sense! Patch (hopefully) coming soon for this.
-Zander
On Wednesday, April 29th, 2026 at 10:40 AM, Guinevere Larsen <guinevere@redhat.com> wrote:
> On 4/29/26 9:45 AM, Zander Work via Gdb wrote:
> > Hello,
> >
> > I'm interested in writing a patch for GDB which allows a user to change the radix used for displaying function offsets in instruction listings (example below), right now it only uses decimal, and doesn't respect the existing radix settings (either `radix` or `output-radix`).
> >
> > I want to contribute a patch that allows the user to change the radix used for displaying these offsets, but I'm not sure if it would be best to re-use the value of `output-radix`, or to define a new setting (eg, `offset-radix` maybe).
> >
> > Additionally, if a new option should be added, would it be appropriate to have `set radix` also set that new one (I would assume yes).
> >
> > Does anyone have any opinions on this? My personal feeling is that reusing `output-radix` would be best.
>
> In this case, based on how "set radix" is described in the manual, I
> think this is actually a bug and the offset should already be using the
> specified (output-)radix, so I guess I am with you on the opinion, but
> from the POV that it should already be happening and you're fixing a
> bug, not that it is a feature being extended
>
> --
> Cheers,
> Guinevere Larsen
> It/she
>
> >
> > ---
> >
> > (gdb) set radix 16
> > Input and output radices now set to decimal 16, hex 10, octal 20.
> > (gdb) x/8i $rip
> > => 0x7ffff7fe0c00 <_start>: mov %rsp,%rdi
> > 0x7ffff7fe0c03 <_start+3>: call 0x7ffff7fe1750 <_dl_start>
> > 0x7ffff7fe0c08 <_dl_start_user>: mov %rax,%r12
> > 0x7ffff7fe0c0b <_dl_start_user+3>: mov %rsp,%r13
> > 0x7ffff7fe0c0e <_dl_start_user+6>: mov 0x1cb9c(%rip),%edx # 0x7ffff7ffd7b0 <_rtld_global+1968>
> > 0x7ffff7fe0c14 <_dl_start_user+12>: test $0x2,%edx
> > 0x7ffff7fe0c1a <_dl_start_user+18>: je 0x7ffff7fe0c2d <_dl_start_user+37>
> > 0x7ffff7fe0c1c <_dl_start_user+20>: mov $0x1,%esi
> > ^^ i am referring to these offsets
> >
> >
>
>
prev parent reply other threads:[~2026-04-30 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 12:45 Zander Work via Gdb
2026-04-29 14:40 ` Guinevere Larsen via Gdb
2026-04-30 15:46 ` Zander Work via Gdb [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='-tT8gWCj1g1GjvJRl43XWZw617t_INK4DMPtVHfOvkCNNIFLeYs2Fylz6xQLXmVXqo69m-h3iMq4yFB9WDuZCrQKeVqtRDlOGO1lAbt9AXc=@zanderwork.com' \
--to=gdb@sourceware.org \
--cc=guinevere@redhat.com \
--cc=zander@zanderwork.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