From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by sourceware.org (Postfix) with ESMTP id 391BE385500F for ; Tue, 22 Jun 2021 02:16:21 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 391BE385500F Received: from vapier (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id 378E6335D4B; Tue, 22 Jun 2021 02:16:20 +0000 (UTC) Date: Mon, 21 Jun 2021 22:16:19 -0400 From: Mike Frysinger To: Fredrik Hederstierna Cc: Simon Marchi , Paul Mathieu , "gdb-patches@sourceware.org" Subject: Re: [PATCH] gdb: add support for handling core dumps on arm-none-eabi Message-ID: Mail-Followup-To: Fredrik Hederstierna , Simon Marchi , Paul Mathieu , "gdb-patches@sourceware.org" References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Spam-Status: No, score=-4.9 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_PASS, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org 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: , X-List-Received-Date: Tue, 22 Jun 2021 02:16:23 -0000 On 25 Oct 2020 21:06, Fredrik Hederstierna via Gdb-patches wrote: > From: Simon Marchi > > Luis and Alan (both GDB ARM maintainers) also expressed the desire to > > have the format documented.  Alan suggested a section in the GDB manual, > > in the ARM-specific section.  I think it is a good idea.  This is > > important, so we have something to point to when people ask "what format > > should I generate so GDB can read it". > > Yes, it was suggested by someone to adding an arm-none section in "G.5.3 ARM Features". > How to proceed on this? I guess the current design is same as *ix minus all specific *ix parts that could be stripped out from documentation. good use for the wiki ? -mike