This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug go/64999] s390x libgo test failure in TestMemoryProfiler
- From: "ian at airs dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 12 Feb 2015 16:45:34 +0000
- Subject: [Bug go/64999] s390x libgo test failure in TestMemoryProfiler
- Auto-submitted: auto-generated
- References: <bug-64999-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64999
--- Comment #11 from Ian Lance Taylor <ian at airs dot com> ---
libbacktrace is all about stack backtraces. It is not about handling
exceptions.
libbacktrace handles inlined calls and hand written trampolines, assuming the
DWARF information is correct. libbacktrace does not currently handle sibling
calls; it could, based on http://www.dwarfstd.org/ShowIssue.php?issue=100909.2,
but nobody has implemented it.
The glibc backtrace_symbols call is a simpler function that is not nearly as
powerful as libbacktrace.