This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: ARM abort() core files

From: Ian Lance Taylor <iant at google dot com>
To: "Hammer\, Tim" <Tim dot Hammer at xerox dot com>
Cc: <gcc at gcc dot gnu dot org>
Date: Tue, 25 Oct 2011 11:50:40 -0700
Subject: Re: ARM abort() core files
References: <42DF740CBF5256498541B6CA6DB6E56D09D31647@USA7061MS03.na.xerox.net>

"Hammer, Tim" <Tim.Hammer@xerox.com> writes:

> About 3 years ago (August, 2008) there was a discussion here about (not) getting a backtrace from abort(3) on ARM:
> ÂÂÂÂ http://gcc.gnu.org/ml/gcc/2008-08/msg00060.html 
>
> That thread discussed why core files generated from a call to abort() do not have a stack to review and some possible approaches for modifying the compiler. I can find no resolution to that discussion nor any other discussion of the topic.
>
> Our toolchain vendor is currently only providing GCC 4.4 and I have verified the issue still exists. They informed me today that GCC 4.6 "may be better about it". Can someone confirm that a change has been made and where I can find more information about it?


This message would have been more appropriate for the mailing list
gcc-help@gcc.gnu.org.  Please take any followups to gcc-help.  Thanks.

This problem was fixed in the gcc 4.5 release with this patch:

http://gcc.gnu.org/ml/gcc-patches/2009-11/msg01234.html

Ian

References:
- ARM abort() core files
  - From: Hammer, Tim

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]