From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id HsV+McHkXWBURAAAWB0awg (envelope-from ) for ; Fri, 26 Mar 2021 09:42:25 -0400 Received: by simark.ca (Postfix, from userid 112) id BBED51EF7C; Fri, 26 Mar 2021 09:42:25 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id DA17A1E789 for ; Fri, 26 Mar 2021 09:42:24 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 32B223858024; Fri, 26 Mar 2021 13:42:24 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 32B223858024 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1616766144; bh=FCvcn05JMWrwwAflc3CALTqbw7OftAtAVatZyGlIeVc=; h=To:Subject:Date:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:From; b=lOLInkeB4tdy3eAfyVnOt/LnGCzJRboQOMbmV1BAbk9Qo78+n/UqBPLCpq1cY1HjH veqASo55DhB9dH8Cu+OY8Pgw/kImTvO7b3kapMY8MyC7F+FxOZOoeQ8P6AR74yblC8 ttv7nzBSFo60Q4WiWb7D6KXXifnndmkiEBFJ/BPg= Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) by sourceware.org (Postfix) with ESMTPS id 374B43858024 for ; Fri, 26 Mar 2021 13:42:20 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 374B43858024 Received: by mail-qt1-x82f.google.com with SMTP id i19so4204926qtv.7 for ; Fri, 26 Mar 2021 06:42:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=FCvcn05JMWrwwAflc3CALTqbw7OftAtAVatZyGlIeVc=; b=nOtnIYOFzUJKoSJ71jOnr6O1bhzqBpNeSeYTHRaieAXD1vErbRnHkul2xvTuSx9l/6 Hj3fEbq7RcjTN7fxosOJBTL9a5r5OEn5djnQoasevQj4pILkiL9mbZl1OALMyu18Zq8U D2twjfIYAPpT5VZMWe+6aVqZ9r+0pV5yQ2U1bMJOCwb2nNAHxCTPVwI2OmILb3ienJ3q +oDEtAN5Vyljkh13dyBoZv1S/cVvHRhsTNNVva7+l1pLyt8TjqZP7//r1ql0AHhDzjGr EtXAroOdU/9IBqQE7RtSH0u7gkjfrEmI55cf2rbgZ8uc18w7KsAUEjJsce/Ba/MRQJEP u11w== X-Gm-Message-State: AOAM5316iH1GCoIIltUolnrSXVQpZvtW63/F78Lqif0iWR+WqZrTCySU nIP5dUI7lW4Uu4D7yqBG/w5VBnuq6TxL9g== X-Google-Smtp-Source: ABdhPJzm/qoULIBf6nDn5zSsrgROZSJhUGVw4GrPQ/vkpF4BbiQwlOYx2klurAKHXqP/BEO1N50qWg== X-Received: by 2002:a05:622a:1647:: with SMTP id y7mr11972024qtj.210.1616766139760; Fri, 26 Mar 2021 06:42:19 -0700 (PDT) Received: from localhost.localdomain ([2804:7f0:4841:2841:c18:e543:6db3:6ca3]) by smtp.gmail.com with ESMTPSA id b22sm6770435qkk.45.2021.03.26.06.42.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 26 Mar 2021 06:42:18 -0700 (PDT) To: gdb-patches@sourceware.org Subject: [PATCH] [doc] Fix memory tagging section type Date: Fri, 26 Mar 2021 10:42:14 -0300 Message-Id: <20210326134214.543829-1-luis.machado@linaro.org> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Luis Machado via Gdb-patches Reply-To: Luis Machado Errors-To: gdb-patches-bounces@sourceware.org Sender: "Gdb-patches" 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 * 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