Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Guinevere Larsen <guinevere@redhat.com>,
	Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: Introduce user-friendly namespace identifier for "info shared"
Date: Mon, 17 Mar 2025 11:36:18 -0400	[thread overview]
Message-ID: <c7a8dbe9-857d-42a6-852f-32363700eccb@simark.ca> (raw)
In-Reply-To: <ce30ec44-7b72-498d-a601-e3e752db449a@redhat.com>

On 3/17/25 7:55 AM, Guinevere Larsen wrote:
> I can give this a shot, but in my head there are 2 ways of implementing it:
> 
> 1. If there is more than one linker namespace *active* when the command is run;
> 2. If there is more than one linker namespace *registered* when the command is run;
> 
> The main difference is: if the inferior has opened an SO in a namespace, but has since closed it and everything loaded is in the default namespace, should we still have the NS column? The first is closer to a future plan of having an "active namespaces" convenience variable, while the second is brand new code that I don't expect to use anywhere else, but I can see an argument for it, so which do you prefer?

I don't know much about linker namespaces, so I don't know which option
is better, but I agree that not showing the column when the program
doesn't deal with non-default namespaces would be nice.  We do something
similar for instance with info threads: if there is a single inferior,
we don't show the inferior number in the thread id, otherwise we do.

Simon

  reply	other threads:[~2025-03-17 16:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-13 17:00 Guinevere Larsen
2025-03-13 19:19 ` Eli Zaretskii
2025-03-13 19:27   ` Guinevere Larsen
2025-03-15  2:51 ` Kevin Buettner
2025-03-15  3:11   ` Kevin Buettner
2025-03-17 11:55     ` Guinevere Larsen
2025-03-17 15:36       ` Simon Marchi [this message]
2025-03-18  1:07       ` Kevin Buettner
2025-03-17 15:36 ` Simon Marchi
2025-03-17 17:07   ` Guinevere Larsen
2025-03-17 17:54     ` Simon Marchi
2025-03-19 12:30 ` [PATCH v2] " Guinevere Larsen
2025-03-21 17:55   ` Guinevere Larsen
2025-03-27 17:13   ` [PATCH v3] " Guinevere Larsen
2025-03-31 19:34     ` Guinevere Larsen
2025-04-05 20:17     ` Kevin Buettner
2025-04-07 13:07       ` 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=c7a8dbe9-857d-42a6-852f-32363700eccb@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=guinevere@redhat.com \
    --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