Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

named dies immediately with libpthread problem

With current (after time_t changes), named is giving me a segv straightaway.
(Both with chroot version and non-chroot version).

Running a backtrace gives many thousands of __sigtimedwait50() recursive
calls then gdb falls over.  

(gdb) bt
#0  0xbba2ec05 in __sigtimedwait50 () from /usr/lib/
#1  0xbba2ec35 in __sigtimedwait50 () from /usr/lib/
#2  0xbba2ec35 in __sigtimedwait50 () from /usr/lib/
#14512 0xbba2ec35 in __sigtimedwait50 () from /usr/lib/

[1]    6260 segmentation fault (core dumped)  gdb named/named named.core

I've rebuilt it from a clean usr.sbin/bind dir but I'm rebuilding everything
again from scratch now.  Also, I had librump blow up with building .S files
from arch/i386/atomic/ due to -traditional-cpp requirements.


Home | Main Index | Thread Index | Old Index