From: Guinevere Larsen <guinevere@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/3] Add some linker namespaces conveniences
Date: Wed, 9 Apr 2025 17:20:38 -0300 [thread overview]
Message-ID: <f390a6f6-1344-4289-b6b3-e3ee3c024f2b@redhat.com> (raw)
In-Reply-To: <20250407110851.18e596fd@f41-zbm-amd>
On 4/7/25 3:08 PM, Kevin Buettner wrote:
> On Mon, 7 Apr 2025 11:54:40 -0300
> Guinevere Larsen <guinevere@redhat.com> wrote:
>
>> This series is a second step in improving the User Experience of
>> debugging inferiors with multiple namespaces. It adds 2 things to make
>> it more convenient for users to understand what the inferior is doing.
>>
>> The first patch adds convenience variables, specifically _active_namespaces
>> and _current_namespaces. These can be used to track where in the execution
>> of an inferior the user is, and could be used in breakpoint conditions
>> to stop at a specific namespace.
>>
>> The third patch adds a new command, "info namespaces", to help the user
>> check what solibs are loaded, and where. To make the patch more
>> readable, the second patch is a minor refactor of the command "info
>> sharedlibrary".
> I'm wondering if we want "namespaces" to mean "linker namespaces". I
> can imagine someone adding a command to iterate over the
> DW_TAG_namespace entries in the available DWARF info and then print
> things regarding those entries. That too could be a good (possibly
> better) candidate for a GDB "info namespaces" command.
>
> What I'm suggesting here is that we might want to add a qualifier to
> the command and related names, i.e. that the new command be named
> "info linker-namespaces" instead of just "info namespaces". Likewise,
> add qualifiers for _active_namespaces and _current_namespaces.
This makes sense. I'm working on this change locally and will send a v2
shortly.
>
> Kevin
>
--
Cheers,
Guinevere Larsen
She/Her/Hers
prev parent reply other threads:[~2025-04-09 20:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 14:54 Guinevere Larsen
2025-04-07 14:54 ` [PATCH 1/3] gdb: add convenience variables around linker namespace debugging Guinevere Larsen
2025-04-07 15:39 ` Eli Zaretskii
2025-04-07 17:10 ` Guinevere Larsen
2025-04-07 14:54 ` [PATCH 2/3] gdb: factor out printing a table of solibs for info sharedlibrary Guinevere Larsen
2025-04-07 14:54 ` [PATCH 3/3] GDB: Introduce "info namespaces" command Guinevere Larsen
2025-04-07 15:45 ` Eli Zaretskii
2025-04-07 17:04 ` Guinevere Larsen
2025-04-07 18:08 ` [PATCH 0/3] Add some linker namespaces conveniences Kevin Buettner
2025-04-09 20:20 ` Guinevere Larsen [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=f390a6f6-1344-4289-b6b3-e3ee3c024f2b@redhat.com \
--to=guinevere@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@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