From: Guinevere Larsen <guinevere@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH v3 1/3] gdb: add convenience variables around linker namespace debugging
Date: Tue, 22 Apr 2025 09:41:21 -0300 [thread overview]
Message-ID: <666338c3-951f-4437-960f-38bbba159794@redhat.com> (raw)
In-Reply-To: <87zfgd702d.fsf@tromey.com>
On 4/18/25 4:15 PM, Tom Tromey wrote:
>>>>>> "Guinevere" == Guinevere Larsen <guinevere@redhat.com> writes:
> Guinevere> + In systems that don't support linkage namespaces, these always return 1
> Guinevere> + and [[0]] respectively.
>
> What's the reason that this string syntax is chosen rather than, say, an
> integer?
>
> Tom
>
I want to standardize it so whenever GDB prints a namespace identifier,
we always use the same syntax that a user should use to find namespaces.
This has the handy side-effect that, if we decide to use the convenience
variable internally for something else (say, when printing a backtrace)
there is no special handling, we'll only need to print the actual conv
var string.
--
Cheers,
Guinevere Larsen
She/Her/Hers
next prev parent reply other threads:[~2025-04-22 12:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 17:50 [PATCH v3 0/3] Add some linker namespaces conveniences Guinevere Larsen
2025-04-11 17:50 ` [PATCH v3 1/3] gdb: add convenience variables around linker namespace debugging Guinevere Larsen
2025-04-18 19:15 ` Tom Tromey
2025-04-22 12:41 ` Guinevere Larsen [this message]
2025-04-11 17:50 ` [PATCH v3 2/3] gdb: factor out printing a table of solibs for info sharedlibrary Guinevere Larsen
2025-04-11 17:50 ` [PATCH v3 3/3] GDB: Introduce "info namespaces" command Guinevere Larsen
2025-04-17 23:43 ` [PATCH v3 0/3] Add some linker namespaces conveniences Kevin Buettner
2025-04-23 12:44 ` 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=666338c3-951f-4437-960f-38bbba159794@redhat.com \
--to=guinevere@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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