public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/15868] New: backtrace interfaces and calls to noreturn functions
@ 2013-08-20 20:13 jsm28 at gcc dot gnu.org
2014-06-13 13:06 ` [Bug libc/15868] " fweimer at redhat dot com
0 siblings, 1 reply; 2+ messages in thread
From: jsm28 at gcc dot gnu.org @ 2013-08-20 20:13 UTC (permalink / raw)
To: glibc-bugs
http://sourceware.org/bugzilla/show_bug.cgi?id=15868
Bug ID: 15868
Summary: backtrace interfaces and calls to noreturn functions
Product: glibc
Version: 2.18
Status: NEW
Severity: normal
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: jsm28 at gcc dot gnu.org
CC: drepper.fsp at gmail dot com
Created attachment 7155
--> http://sourceware.org/bugzilla/attachment.cgi?id=7155&action=edit
Testcase
The backtrace / backtrace_symbols / backtrace_symbols_fd interfaces do not work
well when backtracing through calls to noreturn functions (a natural use case -
a noreturn error-handling function might reasonably wish to print a backtrace).
This is illustrated by the attached testcase on x86_64. At least with some GCC
versions, the call to a noreturn function has return address pointing to
padding after the end of the calling function, meaning that it does not point
inside that function and so a name for it cannot be found.
The backtrace interface is that the addresses are return addresses. But
reliable backtracing requires additional information about whether frames are
signal frame, in which case the return address points inside the relevant
function, or not, in which case you should subtract 1 to be sure of being
inside the relevant function. (That involves calling _Unwind_GetIPInfo instead
of _Unwind_GetIP to get the relevant information.) So to support this case
reliably, there should be new interfaces that handle this adjustment in some
way.
(Old discussion started at:
http://www.eglibc.org/archives/patches/msg01077.html .)
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Bug libc/15868] backtrace interfaces and calls to noreturn functions
2013-08-20 20:13 [Bug libc/15868] New: backtrace interfaces and calls to noreturn functions jsm28 at gcc dot gnu.org
@ 2014-06-13 13:06 ` fweimer at redhat dot com
0 siblings, 0 replies; 2+ messages in thread
From: fweimer at redhat dot com @ 2014-06-13 13:06 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=15868
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |security-
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-06-13 13:06 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-08-20 20:13 [Bug libc/15868] New: backtrace interfaces and calls to noreturn functions jsm28 at gcc dot gnu.org
2014-06-13 13:06 ` [Bug libc/15868] " fweimer at redhat dot com
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).