From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13008 invoked by alias); 31 Oct 2006 19:10:35 -0000 Received: (qmail 12992 invoked by uid 22791); 31 Oct 2006 19:10:34 -0000 X-Spam-Check-By: sourceware.org Received: from bethe.phy.uc.edu (HELO physics.uc.edu) (129.137.4.14) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 31 Oct 2006 19:10:23 +0000 Received: from earth.phy.uc.edu (earth.phy.uc.edu [10.44.11.234]) by physics.uc.edu (8.13.6/8.13.4) with ESMTP id k9VJAKxj010652; Tue, 31 Oct 2006 14:10:20 -0500 Received: from localhost.localdomain (earth [127.0.0.1]) by earth.phy.uc.edu (8.13.7/8.13.7) with ESMTP id k9VJD3Af027527; Tue, 31 Oct 2006 14:13:03 -0500 Received: (from pinskia@localhost) by localhost.localdomain (8.13.7/8.13.7/Submit) id k9VJD2O9027526; Tue, 31 Oct 2006 14:13:02 -0500 From: Andrew Pinski Message-Id: <200610311913.k9VJD2O9027526@localhost.localdomain> Subject: Re: [Bug libfortran/29649] Force core dump on runtime library errors To: gcc-bugzilla@gcc.gnu.org Date: Tue, 31 Oct 2006 19:10:00 -0000 Cc: gcc-bugs@gcc.gnu.org In-Reply-To: <20061031183739.17636.qmail@sourceware.org> X-Mailer: ELM [version 2.5 PL8] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Score: -2.4 () ALL_TRUSTED X-IsSubscribed: yes Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-10/txt/msg02724.txt.bz2 List-Id: > - Support for coredumps (compile time? Environment variable? The latter > overwriting the former?) > [Advantage compile-time option: The core is there, if one needs it. Advantage > run-time option: One can quickly turn it on, if needed.] > > - Traceback support more or less as outlined above (comment 4, comment 3), > which prints only the Hex address (similar to the unwind.diff, attachment > 12519) or the backtrace_symbols() example in comment 3). One should mention the > addr2line program in the manpage/manual. > > - Optionally, linking with libbfd and providing symbol-resolved traceback. Unless you want to make your program GPL, I would go against this. This is why for libgcj, they have not linked it in yet. -- Pinski