Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Guinevere Larsen <guinevere@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3] gdb/doc: Explain linker namespaces
Date: Mon, 16 Jun 2025 15:27:04 +0300	[thread overview]
Message-ID: <86v7ovoorr.fsf@gnu.org> (raw)
In-Reply-To: <20250616115521.12950-1-guinevere@redhat.com> (message from Guinevere Larsen on Mon, 16 Jun 2025 08:55:21 -0300)

> From: Guinevere Larsen <guinevere@redhat.com>
> Cc: Guinevere Larsen <guinevere@redhat.com>
> Date: Mon, 16 Jun 2025 08:55:21 -0300
> 
> Recent GDB commits added more features related to linker namespaces and
> documented them on the manual, but did not add a convenient way for a
> user to understand what they are. This commit adds a quick explanation
> of what they are.
> 
> It also fixes the inconsistency of using "linker namespaces" and
> "linkage namespaces", by always using the first form to avoid user
> confusion.
> ---
>  gdb/doc/gdb.texinfo | 23 +++++++++++++++--------
>  1 file changed, 15 insertions(+), 8 deletions(-)

Thanks, this is okay, with two minor comments:

> +@cindex linker namespaces
> +Linker namespaces are a feature of some standard libraries, that allow

Please enclose "Linker namespaces" in @dfn, as this text introduces
new terminology.

> +shared objects to be loaded in isolated environment, eliminating the
> +possibility that those objects may cross-talk.  Each set of isolated
> +shared objects is said to belong to a "namespace", and linker related

The "namespace" part should be quote ``like this'', i.e. with single
quoting characters -- this will produce nicer results in the printed
output.

Approved-By: Eli Zaretskii <eliz@gnu.org>

  reply	other threads:[~2025-06-16 12:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-06 15:24 [PATCH] " Guinevere Larsen
2025-06-06 18:48 ` Eli Zaretskii
2025-06-06 19:00   ` Guinevere Larsen
2025-06-06 19:13     ` Eli Zaretskii
2025-06-06 19:45 ` [PATCH v2] " Guinevere Larsen
2025-06-06 19:58   ` Eli Zaretskii
2025-06-16 11:55   ` [PATCH v3] " Guinevere Larsen
2025-06-16 12:27     ` Eli Zaretskii [this message]
2025-06-16 20:17       ` 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=86v7ovoorr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=guinevere@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