From: Eli Zaretskii <eliz@gnu.org>
To: Guinevere Larsen <guinevere@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/doc: Explain linker namespaces
Date: Fri, 06 Jun 2025 21:48:44 +0300 [thread overview]
Message-ID: <86frgcln8z.fsf@gnu.org> (raw)
In-Reply-To: <20250606152423.567047-1-guinevere@redhat.com> (message from Guinevere Larsen on Fri, 6 Jun 2025 12:24:23 -0300)
> From: Guinevere Larsen <guinevere@redhat.com>
> Cc: eliz@gnu.org,
> Guinevere Larsen <guinevere@redhat.com>
> Date: Fri, 6 Jun 2025 12:24:23 -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 | 15 +++++++++++----
> 1 file changed, 11 insertions(+), 4 deletions(-)
Thanks.
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -13106,8 +13106,8 @@ environment variable.
>
> @vindex $_active_linker_namespaces@r{, convenience variable}
> @item $_active_linker_namespaces
> -Number of active linkage namespaces in the inferior. In systems with no
> -support for linkage namespaces, this variable will always be set to @samp{1}.
> +Number of active linker namespaces in the inferior. In systems with no
> +support for linker namespaces, this variable will always be set to @samp{1}.
Please add here a cross-reference to where linker namespaces are
described.
> +@cindex Linker Namespaces
Index entries should try not to use upper-case letters, unless really
necessary. This is because in some locales upper-case letters'
sorting order is different from the US-ASCII locale, and we don't want
the sorting of the index entries depend on the locale where the manual
is produced.
> +Linker namespaces are a feature of some standard libraries, that allow
> +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
Please use ``namespace'', not "namespace". The former produces
prettier output in the printed version of the manual.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
next prev parent reply other threads:[~2025-06-06 18:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 15:24 Guinevere Larsen
2025-06-06 18:48 ` Eli Zaretskii [this message]
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
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=86frgcln8z.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