http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54572
--- Comment #8 from Ian Lance Taylor <ian at airs dot com> 2012-11-26 23:08:45 UTC --- The crash within libbacktrace is occurring as it tries to read the debug info. This is presumably a bug in libbacktrace, but I don't know what the problem is without more information. libbacktrace is pretty careful to only read memory that was explicitly read. There is presumably a bug there, but I don't know what it is. I doubt the fact that a signal occurred has anything to do with this. There seems to be something odd about the debug info, as shown both by the fact that libbacktrace crashes trying to read it and that gdb does not display file/line information.
