From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by sourceware.org (Postfix) with ESMTP id 523943858437 for ; Tue, 31 Aug 2021 11:17:53 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 523943858437 Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-43-FBhZn4KEPWWornHJoY96Mg-1; Tue, 31 Aug 2021 07:17:51 -0400 X-MC-Unique: FBhZn4KEPWWornHJoY96Mg-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id A24B91008061; Tue, 31 Aug 2021 11:17:50 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.39.194.140]) by smtp.corp.redhat.com (Postfix) with ESMTPS id C9D5E10016FF; Tue, 31 Aug 2021 11:17:49 +0000 (UTC) From: Florian Weimer To: Andrew Burgess Cc: gdb-patches@sourceware.org Subject: Re: [PATCH 0/6] Display GDB backtrace for internal errors References: Date: Tue, 31 Aug 2021 13:17:47 +0200 In-Reply-To: (Andrew Burgess's message of "Thu, 19 Aug 2021 10:49:25 +0100") Message-ID: <8735qplv6s.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-6.7 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) 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, 31 Aug 2021 11:17:54 -0000 * Andrew Burgess: > This series does two things: > > 1. Imports libbacktrace from gcc to present better backtraces of > GDB when we hit a fatal signal, and > > 2. Prints the backtrace when GDB hits an internal-error (e.g. an > assert). Ideally, we would add this capability to bash, so that if a process dies with certain signals, the shell prints a backtrace, possibly with help from a core-catching daemon. Backtrace generation from outside the process is much more reliable. It also avoids introducing further opportunities for exploitation after memory corruption is detected. In my opinion, it does not make much sense to add this functionality to more and more GNU programs. Thanks, Florian