On Thu, Sep 25, 2008 at 09:36:08PM +0200, Manuel Bouyer wrote: > On Thu, Sep 25, 2008 at 12:23:03PM -0700, Bill Stouder-Studenmund wrote: > > Ok. We now set PS_WEXIT a lot later than we used to. Before, we'd set > > P_WEXIT (the old value for this flag) in sigexit(). Now we don't. > > > > Also, the thread that decides to core the whole process will not have > > LW_WEXIT set on itself. So we have to look at PS_WCORE. > > > > Please try rev 1.91.2.43. > > OK, now it doesn't panic, but named gets a SIGSEGV: > Sep 25 21:30:36 lavardin-1 named[393]: starting BIND 9.3.0 > Sep 25 21:30:36 lavardin-1 named[393]: found 1 CPU, using 1 worker thread > Sep 25 21:30:36 lavardin-1 /netbsd: pid 393 (named), uid 0: exited on signal > 11 (core dumped) > > named -g -d20 doens't give more details, nor does ktrace: > [...] > 388 named CALL break(0x819e000) > 388 named RET break 0 > 388 named CALL break(0x819f000) > 388 named RET break 0 > 388 named PSIG SIGSEGV SIG_DFL: code=SEGV_ACCERR, addr=0x0, trap=4) > 388 named NAMI "named.core" > > gdb says: > Core was generated by `named'. > Program terminated with signal 11, Segmentation fault. > Reading symbols from /usr/libexec/ld.elf_so...(no debugging symbols found)... > done. > Loaded symbols for /usr/libexec/ld.elf_so > Reading symbols from /usr/lib/libpthread.so.0...(no debugging symbols > found)... > done. > Loaded symbols for /usr/lib/libpthread.so.0 > Reading symbols from /usr/lib/libc.so.12...(no debugging symbols > found)...doneLoaded symbols for /usr/lib/libc.so.12 > #0 0xbbbe60a9 in _setcontext_u_s87 () from /usr/lib/libpthread.so.0 > (gdb) where > #0 0xbbbe60a9 in _setcontext_u_s87 () from /usr/lib/libpthread.so.0 > #1 0xbbbde21c in pthread__upcall_switch () from /usr/lib/libpthread.so.0 > #2 0xbbbe04a5 in pthread__upcall () from /usr/lib/libpthread.so.0 > > > named has the expected behavior (that is, exit gracefully because there's > no /etc/named.conf) with NetBSD 3.0 and 4.0 kernels. Ok. I think something may be wrong in context handling. I hope not, as I don't really understand all of it & was hoping it just worked from before. I'll see how this does on my system tonight. Take care, Bill
Attachment:
pgpa4ijRNPPkq.pgp
Description: PGP signature