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 22:13:19 +0300 [thread overview]
Message-ID: <86bjr0lm40.fsf@gnu.org> (raw)
In-Reply-To: <de12d48a-7a13-4713-bcfb-47b734c68fb2@redhat.com> (message from Guinevere Larsen on Fri, 6 Jun 2025 16:00:00 -0300)
> Date: Fri, 6 Jun 2025 16:00:00 -0300
> Cc: gdb-patches@sourceware.org
> From: Guinevere Larsen <guinevere@redhat.com>
>
> On 6/6/25 3:48 PM, Eli Zaretskii wrote:
>
> --- 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.
>
> I don't know how to do that, what texinfo macro(? command?) should I use?
Something like this:
Number of active linker namespaces in the inferior (@pxref{Files}).
In systems with no support for linker namespaces, this variable will
always be set to @samp{1}.
next prev parent reply other threads:[~2025-06-06 19:13 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
2025-06-06 19:00 ` Guinevere Larsen
2025-06-06 19:13 ` Eli Zaretskii [this message]
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=86bjr0lm40.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