From: "Schimpe, Christina" <christina.schimpe@intel.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"thiago.bauermann@linaro.org" <thiago.bauermann@linaro.org>
Subject: RE: [PATCH v2 6/9] gdb: Add command option 'bt -shadow' to print the shadow stack backtrace.
Date: Tue, 14 Apr 2026 13:28:52 +0000 [thread overview]
Message-ID: <SN7PR11MB763817D080226986FEC1D77EF9252@SN7PR11MB7638.namprd11.prod.outlook.com> (raw)
In-Reply-To: <86o6jloj0p.fsf@gnu.org>
> -----Original Message-----
> From: Eli Zaretskii <eliz@gnu.org>
> Sent: Dienstag, 14. April 2026 13:53
> To: Schimpe, Christina <christina.schimpe@intel.com>
> Cc: gdb-patches@sourceware.org; thiago.bauermann@linaro.org
> Subject: Re: [PATCH v2 6/9] gdb: Add command option 'bt -shadow' to print
> the shadow stack backtrace.
>
> > From: "Schimpe, Christina" <christina.schimpe@intel.com>
> > CC: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
> > "thiago.bauermann@linaro.org" <thiago.bauermann@linaro.org>
> > Date: Tue, 14 Apr 2026 08:43:52 +0000
> >
> > I just noticed the following warnings on fedora with texinfo 7.2:
> >
> > gdb.texinfo:26867: warning: node next pointer for `AArch64' is `x86'
> > but next is `GCS' in menu
> > gdb.texinfo:27232: warning: node `x86' is next for `GCS' in menu but
> > not in sectioning
> > gdb.texinfo:27232: warning: node `AArch64' is prev for `GCS' in menu
> > but not in sectioning
> > gdb.texinfo:27232: warning: node up pointer for `GCS' is `AArch64' but
> > up is `Architectures' in menu
> > gdb.texinfo:27280: warning: node next pointer for `x86' is `Alpha' but
> > next is `CET' in menu
> > gdb.texinfo:27280: warning: node prev pointer for `x86' is `AArch64'
> > but prev is `GCS' in menu
> > gdb.texinfo:27321: warning: node `Alpha' is next for `CET' in menu but
> > not in sectioning
> > gdb.texinfo:27321: warning: node `x86' is prev for `CET' in menu but
> > not in sectioning
> > gdb.texinfo:27321: warning: node up pointer for `CET' is `x86' but up
> > is `Architectures' in menu
> > gdb.texinfo:27362: warning: node prev pointer for `Alpha' is `x86' but
> > prev is `CET' in menu
> >
> > for the menu changes:
> > ~~~
> > @menu
> > * AArch64::
> > +* GCS::
> > * x86::
> > +* CET::
> > * Alpha::
> > * MIPS::
> > * HPPA::
> > ~~~
>
> Yes, because you are adding these items to the wrong menu. These nodes are
> NOT subsections of "Architectures", they are subsubsections of its
> subsections. So the @menu with these nodes should be in the parent
> subsections, not in "Architectures".
It appears there was a misunderstanding on my part—thank you for the clarification.
I thought you meant that menu with "parent menu" in your feedback before,
since there is currently no menu in the parent subsections.
> > If I change the CET and GCS subsubsections to subsections the warning
> disappears...
> > so I think I must add a new @menu for the subsubsections.
> >
> > +@menu
> > +* CET::
> > +@end menu
>
> Yes.
>
> > This avoids triggering a warning. However, since none of the other
> > AArch64 or
> > x86 subsubsections currently have nodes, I believe we should add nodes
> > for them and update the menu accordingly:
>
> There's no need to add a node for each subsubsection.
Won't this help us to navigate using 'previous' and 'next' etc. when using "info gdb" ?
> In fact, I'm not sure I
> understand why you wanted to add the two @node's that give you trouble,
> can you explain?
You mean the nodes for CET and GCS?
If I don't add them, I'll see
~~~
gdb.texinfo:8801: @pxref reference to nonexistent node `CET'
gdb.texinfo:8822: @pxref reference to nonexistent node `CET'
~~~
Christina
Intel Deutschland GmbH
Registered Address: Dornacher Strasse 1, 85622 Feldkirchen, Germany
Tel: +49 89 991 430, www.intel.de
Managing Directors: Harry Demas, Jeffrey Schneiderman, Yin Chong Sorrell
Chairperson of the Supervisory Board: Nicole Lau
Registered Seat: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2026-04-14 13:29 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 8:05 [PATCH v2 0/9] Add new command " Christina Schimpe
2026-01-23 8:05 ` [PATCH v2 1/9] gdb: Generalize handling of the shadow stack pointer Christina Schimpe
2026-02-19 17:55 ` Tom Tromey
2026-02-27 18:09 ` Schimpe, Christina
2026-02-27 18:26 ` Tom Tromey
2026-03-02 11:53 ` Schimpe, Christina
2026-04-09 9:49 ` Schimpe, Christina
2026-04-14 17:34 ` Tom Tromey
2026-04-15 7:35 ` Schimpe, Christina
2026-04-15 15:54 ` Tom Tromey
2026-02-27 22:54 ` Thiago Jung Bauermann
2026-03-06 3:15 ` Thiago Jung Bauermann
2026-03-06 3:57 ` Thiago Jung Bauermann
2026-04-09 11:57 ` Schimpe, Christina
2026-04-10 5:03 ` Thiago Jung Bauermann
2026-04-10 7:53 ` Schimpe, Christina
2026-04-09 12:06 ` Schimpe, Christina
2026-04-10 5:05 ` Thiago Jung Bauermann
2026-01-23 8:05 ` [PATCH v2 2/9] gdb: Refactor 'stack.c:print_frame' Christina Schimpe
2026-01-23 8:05 ` [PATCH v2 3/9] gdb: Introduce 'stack.c:print_pc' function without frame argument Christina Schimpe
2026-01-23 8:05 ` [PATCH v2 4/9] gdb: Refactor 'find_symbol_funname' and 'info_frame_command_core' in stack.c Christina Schimpe
2026-02-19 17:32 ` Tom Tromey
2026-04-09 12:40 ` Schimpe, Christina
2026-01-23 8:05 ` [PATCH v2 5/9] gdb: Refactor 'stack.c:print_frame_info' Christina Schimpe
2026-01-23 8:05 ` [PATCH v2 6/9] gdb: Add command option 'bt -shadow' to print the shadow stack backtrace Christina Schimpe
2026-01-23 8:52 ` Eli Zaretskii
2026-02-13 16:42 ` Schimpe, Christina
2026-04-14 8:43 ` Schimpe, Christina
2026-04-14 11:53 ` Eli Zaretskii
2026-04-14 13:28 ` Schimpe, Christina [this message]
2026-04-14 14:12 ` Eli Zaretskii
2026-04-14 15:05 ` Schimpe, Christina
2026-02-19 18:19 ` Tom Tromey
2026-04-09 16:48 ` Schimpe, Christina
2026-03-06 4:31 ` Thiago Jung Bauermann
2026-03-06 9:39 ` Schimpe, Christina
2026-04-09 15:12 ` Schimpe, Christina
2026-04-10 6:21 ` Thiago Jung Bauermann
2026-04-10 12:12 ` Schimpe, Christina
2026-01-23 8:05 ` [PATCH v2 7/9] gdb: Provide gdbarch hook to distinguish shadow stack backtrace elements Christina Schimpe
2026-01-23 8:47 ` Eli Zaretskii
2026-02-19 17:41 ` Tom Tromey
2026-01-23 8:05 ` [PATCH v2 8/9] gdb: Implement the hook 'is_no_return_shadow_stack_address' for amd64 linux Christina Schimpe
2026-02-19 17:43 ` Tom Tromey
2026-01-23 8:05 ` [PATCH v2 9/9] gdb, mi: Add -shadow-stack-list-frames command Christina Schimpe
2026-01-23 8:46 ` Eli Zaretskii
2026-02-13 19:17 ` Schimpe, Christina
2026-02-19 18:26 ` Tom Tromey
2026-03-02 12:39 ` [PATCH v2 0/9] Add new command to print the shadow stack backtrace Schimpe, Christina
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=SN7PR11MB763817D080226986FEC1D77EF9252@SN7PR11MB7638.namprd11.prod.outlook.com \
--to=christina.schimpe@intel.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=thiago.bauermann@linaro.org \
/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