Stacktraces and Glibc
This is from HJ Lu's announcement for his forked gdb:
=====
Problems:
Because most of system calls in glibc 2 are written in assembly without
frame pointer, gdb may not be able to debug nor get stack trace system
calls on glibc-based 2 systems. Due to this, "make check" may fail in
FAIL: gdb.base/a1-selftest.exp: backtrace through signal handler
FAIL: gdb.base/signals.exp: bt in signals.exp
with glibc 2.
=====
could that be "our" problem where stack traces