Re: aborted thread backtrace stops at sighandler call

Mark Kettenis
2005-06-25T15:28:23Z

Date: Fri, 24 Jun 2005 11:11:29 -0400
From: Louis LeBlanc <dev@keyslapper.net>

Looked a bit closer into this.

This is the backtrace for the aborted thread:
(gdb) bt
#0 0xfea1f82c in __tbl_2_huge_digits () from /usr/lib/libc.so.1
#1 0xfe9d0a24 in sysconf () from /usr/lib/libc.so.1
#2 0xfe9b6ce0 in ascftime () from /usr/lib/libc.so.1
#3 0x0003c72c in XPCSigCheck (Sig=11, Info=0xfe776ad0, Context=0xfe776818) at xpcsig.c:347
#4 0xff365b14 in ?? ()
#5 0xff365b18 in ?? ()
Previous frame identical to this frame (corrupt stack?)

This backtrace is weird. __tbl_2_huge_digits isn't a function but
some sort of data structure. No surprise that gdb's unwinder gets
confused! For some reason gdb's symbol reader made a mistake when
reading in the symbols for /usr/lib/libc.so.1.

Mark