https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67414
Janne Blomqvist <jb at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2015-08-31
CC| |fxcoudert at gcc dot gnu.org,
| |jb at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Janne Blomqvist <jb at gcc dot gnu.org> ---
Confirmed.
I'd say this is a WONTFIX. The reason is that with the new libbacktrace-based
backtrace code the backtrace is generated in the same process, whereas the old
implementation forked a copy of addr2line which did the symbol lookup. So when
the code fails due to bumping into the memory limit, generating the backtrace
fails. However, as there are several benefits of the new libbacktrace way, I
don't think we want to go back to the old addr2line way.
That being said, I have a patch which 1) Improves the error message for
backtracing failing 2) Fixes the root case for the segfault here. Fixing issue
2) actually makes the backtrace go away, so uh.. Well, that's more an issue for
PR 53379 anyway.
