From: Ian Lance Taylor <iant@google.com>
To: "Hammer\, Tim" <Tim.Hammer@xerox.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: ARM abort() core files
Date: Wed, 26 Oct 2011 01:55:00 -0000 [thread overview]
Message-ID: <mcrobx4c3cv.fsf@dhcp-172-18-216-180.mtv.corp.google.com> (raw)
In-Reply-To: <42DF740CBF5256498541B6CA6DB6E56D09D31647@USA7061MS03.na.xerox.net> (Tim Hammer's message of "Tue, 25 Oct 2011 11:42:39 -0700")
"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
prev parent reply other threads:[~2011-10-25 18:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 0:25 Hammer, Tim
2011-10-26 1:55 ` Ian Lance Taylor [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mcrobx4c3cv.fsf@dhcp-172-18-216-180.mtv.corp.google.com \
--to=iant@google.com \
--cc=Tim.Hammer@xerox.com \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).