From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19773 invoked by alias); 6 Aug 2008 15:51:48 -0000 Received: (qmail 19757 invoked by uid 22791); 6 Aug 2008 15:51:47 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 06 Aug 2008 15:51:08 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 0EC95983EF; Wed, 6 Aug 2008 15:51:07 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id E1CCD98337; Wed, 6 Aug 2008 15:51:06 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1KQlI2-00008i-9l; Wed, 06 Aug 2008 11:51:06 -0400 Date: Wed, 06 Aug 2008 15:51:00 -0000 From: Daniel Jacobowitz To: Mark Kettenis Cc: gcc@sources.redhat.com, sposelenov@emcraft.com, gdb@sources.redhat.com Subject: Re: Problem reading corefiles on ARM Message-ID: <20080806155106.GA500@caradoc.them.org> Mail-Followup-To: Mark Kettenis , gcc@sources.redhat.com, sposelenov@emcraft.com, gdb@sources.redhat.com References: <4899C0FE.4010008@emcraft.com> <20080806152736.GA31492@caradoc.them.org> <200808061542.m76FgmUv017348@brahms.sibelius.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200808061542.m76FgmUv017348@brahms.sibelius.xs4all.nl> User-Agent: Mutt/1.5.17 (2008-05-11) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-08/txt/msg00104.txt.bz2 On Wed, Aug 06, 2008 at 05:42:48PM +0200, Mark Kettenis wrote: > GCC should really not do this. People are almost guaranteed to want > to be able to see a backtrace from abort(3). Yes, it's come up for discussion several times... I don't like the current behavior either. The current behavior was added many years ago for an unspecified application :-( /* Decide if the current function is volatile. Such functions never return, and many memory cycles can be saved by not storing register values that will never be needed again. This optimization was added to speed up context switching in a kernel application. */ IMO that shouldn't be written in C, then... -- Daniel Jacobowitz CodeSourcery