[Bug libc/19292] New: Improve __assert_fail debuggability
avi@cloudius-systems.com
sourceware-bugzilla@sourceware.org
Wed Nov 25 12:03:00 GMT 2015
https://sourceware.org/bugzilla/show_bug.cgi?id=19292
Bug ID: 19292
Summary: Improve __assert_fail debuggability
Product: glibc
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: avi@cloudius-systems.com
CC: drepper.fsp at gmail dot com
Target Milestone: ---
Often when one is debugging an assert(), the variables in the frame that
triggered the assertion failure are marked as "optimized out" by the debugger.
Often this is because the asnprintf() call in __assert_fail() clobbered the
registers they were held in, and so the debugger cannot recover their values.
This can easily be fixed by having __assert_fail() save all registers on its
own stack frame, with an appropriate DWARF annotation, so that the debugger can
inspect the variables' values.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Glibc-bugs
mailing list