Current-Users archive

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

Re: named dies immediately with libpthread problem

In article <>,
Geoff Wing  <> wrote:
>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

That was the epitomy of stupidity on my part. I think it is fixed now.


Home | Main Index | Thread Index | Old Index