From: Zander Work via Gdb <gdb@sourceware.org>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Question about adding a new option vs extending an existing one
Date: Wed, 29 Apr 2026 12:45:42 +0000 [thread overview]
Message-ID: <vFIjU6Ht5QABYhkrHqunljiPWb20nYTIkwU7MCn3OY0yDMMdT19MdgkI3RmG8nR5vC_hKcgnvmM_cMmUMMdhL6p76DcZk2qHoTD7oE35Vb0=@zanderwork.com> (raw)
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.
---
(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
next reply other threads:[~2026-04-29 12:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 12:45 Zander Work via Gdb [this message]
2026-04-29 14:40 ` Guinevere Larsen via Gdb
2026-04-30 15:46 ` Zander Work via Gdb
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='vFIjU6Ht5QABYhkrHqunljiPWb20nYTIkwU7MCn3OY0yDMMdT19MdgkI3RmG8nR5vC_hKcgnvmM_cMmUMMdhL6p76DcZk2qHoTD7oE35Vb0=@zanderwork.com' \
--to=gdb@sourceware.org \
--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