From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id /fHGG/SuYmI94QEAWB0awg (envelope-from ) for ; Fri, 22 Apr 2022 09:34:44 -0400 Received: by simark.ca (Postfix, from userid 112) id 64CC11E058; Fri, 22 Apr 2022 09:34:44 -0400 (EDT) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=Cr3lXh5W; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RDNS_DYNAMIC,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (ip-8-43-85-97.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 E7A7B1E00E for ; Fri, 22 Apr 2022 09:34:43 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 818743856DF7 for ; Fri, 22 Apr 2022 13:34:43 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 818743856DF7 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1650634483; bh=b1Gy56eNPHmvn/qKBDYjFnY81qXWFW+MV+0rPRuRZs4=; h=Date:To:In-Reply-To:Subject:References:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=Cr3lXh5Wtq+T+YVzhVjhjb/MFOHOZO46CqpftjnW9qVjFPjpwVw9F5QEFqxfEeSii DUv5+E5qItiPpfHrQqqo1BO0YvOHWQL1eUU14RNEnS06vrVgVtPz1WFPqwUC1wqPGB 1BwUQV0G9AzGaAE+5aPtXEoIRTDwyxpiIOOTqgto= Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id 99F483858C2C for ; Fri, 22 Apr 2022 13:34:24 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 99F483858C2C Received: from fencepost.gnu.org ([2001:470:142:3::e]:56476) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nhtQ0-0001t7-Io; Fri, 22 Apr 2022 09:34:23 -0400 Received: from [87.69.77.57] (port=1677 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nhtPN-00038t-OC; Fri, 22 Apr 2022 09:33:35 -0400 Date: Fri, 22 Apr 2022 16:33:11 +0300 Message-Id: <83levxp7jc.fsf@gnu.org> To: Luis Machado In-Reply-To: <20220422132715.22723-1-luis.machado@arm.com> (message from Luis Machado via Gdb-patches on Fri, 22 Apr 2022 14:27:15 +0100) Subject: Re: [PATCH 1/2] [AArch64] MTE corefile support References: <20220331140343.9047-1-luis.machado@arm.com> <20220422132715.22723-1-luis.machado@arm.com> 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: Eli Zaretskii via Gdb-patches Reply-To: Eli Zaretskii Cc: gdb-patches@sourceware.org Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" > Date: Fri, 22 Apr 2022 14:27:15 +0100 > From: Luis Machado via Gdb-patches > > diff --git a/gdb/NEWS b/gdb/NEWS > index 760cb2b7abc..d6818d54972 100644 > --- a/gdb/NEWS > +++ b/gdb/NEWS > @@ -3,6 +3,16 @@ > > *** Changes since GDB 12 > > +* GDB now supports dumping memory tag data for AArch64 MTE. It also supports > + reading memory tag data for AArch64 MTE from core files generated by > + the gcore command or the Linux kernel. > + > + When a process uses memory-mapped pages protected by memory tags (for > + example, AArch64 MTE), this additional information will be recorded in > + the core file in the event of a crash or if GDB generates a core file > + from the current process state. GDB will show this additional information > + automatically, or through one of the memory-tag subcommands. > + This part is OK. > diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo > index c1e9b09e833..d9021f1c56d 100644 > --- a/gdb/doc/gdb.texinfo > +++ b/gdb/doc/gdb.texinfo > @@ -25545,6 +25545,24 @@ options that can be controlled at runtime and emulates the @code{prctl} > option @code{PR_SET_TAGGED_ADDR_CTRL}. For further information, see the > documentation in the Linux kernel. > > +@value{GDBN} supports dumping memory tag data to core files through the > +@command{gcore} command and reading memory tag data from core files generated > +by the @command{gcore} command or the Linux kernel. > + > +When a process uses memory-mapped pages protected by memory tags (for > +example, AArch64 MTE), this additional information will be recorded in > +the core file in the event of a crash or if @value{GDB} generates a core file > +from the current process state. > + > +The memory tag data will be used so developers can display the memory > +tags from a particular memory region (using the @samp{m} modifier to the > +@command{x} command, using the @command{print} command or using the various > +@command{memory-tag} subcommands. Please add here cross-references to where the respective commands are described. The documentation parts are okay with that nit fixed. Thanks.