This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/67457] segfault in libbacktrace
- From: "ian at airs dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 08 Sep 2015 14:06:15 +0000
- Subject: [Bug other/67457] segfault in libbacktrace
- Auto-submitted: auto-generated
- References: <bug-67457-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67457
Ian Lance Taylor <ian at airs dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Ian Lance Taylor <ian at airs dot com> ---
I committed a patch so that libbacktrace should no longer segfault when no
memory is available.
If other compilers can print a backtrace when mmap fails, then I think they
must be recording all necessary information in loadable sections. When no
memory is available we could print a trace of PC addresses, but it would be
very painful to print file/line information. We could stage the I/O through a
static buffer, but finding the information to print without being able to build
any data structures would be very inefficient.