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]

ARM abort() core files


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?

Thanks!
--
.Tim 
Tim D. Hammer
Software Developer
Global Business & Services Group
Xerox Corporation
M/S 0111-01A
800 Phillips Road
Webster, NY 14580

Phone: 585/427-1684
Fax:????? 585/231-5596
Mail:???? Tim.Hammer@xerox.com



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