From: Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Subject: [PATCH] [doc] Fix memory tagging section type
Date: Fri, 26 Mar 2021 10:42:14 -0300 [thread overview]
Message-ID: <20210326134214.543829-1-luis.machado@linaro.org> (raw)
It was reported to me that on Ubuntu 14.04 (fairly old) the documentation
fails to build with the following:
gdb/doc/gdb.texinfo:10888: warning: node `Memory' is up for `Memory Tagging' in sectioning but not in menu
gdb/doc/gdb.texinfo:10693: node `Memory' lacks menu item for `Memory Tagging' despite being its Up target
Makefile:491: recipe for target 'gdb.info' failed
make[3]: *** [gdb.info] Error 1
This doesn't seem to happen on Ubuntu 18.04/20.04, but it does make sense.
Fix this by turning @subsection into a @section and adding the
"Memory Tagging" entry to the menu.
gdb/doc/ChangeLog:
YYYY-MM-DD Luis Machado <luis.machado@linaro.org>
* gdb.textinfo (Memory Tagging): Make it a @section and add to the
menu.
---
gdb/doc/gdb.texinfo | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index dbf878cdbc3..7dbffb65d53 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -10118,6 +10118,7 @@ being passed the type of @var{arg} as the argument.
* Arrays:: Artificial arrays
* Output Formats:: Output formats
* Memory:: Examining memory
+* Memory Tagging:: Memory Tagging
* Auto Display:: Automatic display
* Print Settings:: Print settings
* Pretty Printing:: Python pretty printing
@@ -10886,7 +10887,7 @@ target supports computing the CRC checksum of a block of memory
@end table
@node Memory Tagging
-@subsection Memory Tagging
+@section Memory Tagging
Memory tagging is a memory protection technology that uses a pair of tags to
validate memory accesses through pointers. The tags are integer values
--
2.25.1
next reply other threads:[~2021-03-26 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 13:42 Luis Machado via Gdb-patches [this message]
2021-03-26 14:26 ` Eli Zaretskii via Gdb-patches
2021-03-29 14:58 ` Luis Machado via Gdb-patches
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=20210326134214.543829-1-luis.machado@linaro.org \
--to=gdb-patches@sourceware.org \
--cc=luis.machado@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