From: Eli Zaretskii <eliz@gnu.org>
To: Guinevere Larsen <guinevere@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] gdb/doc: Explain linker namespaces
Date: Fri, 06 Jun 2025 22:58:26 +0300 [thread overview]
Message-ID: <867c1olk0t.fsf@gnu.org> (raw)
In-Reply-To: <20250606194533.727963-1-guinevere@redhat.com> (message from Guinevere Larsen on Fri, 6 Jun 2025 16:45:33 -0300)
> From: Guinevere Larsen <guinevere@redhat.com>
> Cc: eliz@gnu.org,
> Guinevere Larsen <guinevere@redhat.com>
> Date: Fri, 6 Jun 2025 16:45:33 -0300
>
> -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(@pxref{Files}). In systems
^^
Please leave a space before the open paren there. These parentheses
are output to the formatted manual, so they need to adhere to rules of
English.
> @vindex $_linker_namespace@r{, convenience variable}
> @item $_linker_namespace
> -The namespace which contains the current location in the inferior. This
> -returns @value{GDBN}'s internal numbering for the namespace. In systems with no
> -support for linker namespaces, this variable will always be set to
> +The namespace which contains the current location in the inferior(@pxref{Files}).
^^^^^^^^^^^^^
There's no need to have the @pxref here, since we just had a cross
reference a dozen lines above.
> @@ -22286,10 +22294,10 @@ conditions or commands as a catchpoint does.
> @item info linker-namespaces
> @item info linker-namespaces @code{[[@var{n}]]}
>
> -With no argument, print the number of linker namespaces which are
> -currently active --- that is, namespaces that have libraries loaded
> -into them. Then, it prints the number of libraries loaded into each
> -namespace, and all the libraries loaded into them, in the same way
> +With no argument, print the number of linker namespaces (@pxref{Files})
Likewise here: the reference is to the same node as the one in which
this text appears, so there's no need to have a cross-reference here.
Thanks.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
next prev parent reply other threads:[~2025-06-06 19:59 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 [this message]
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=867c1olk0t.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