| By Chris Parker <[EMAIL PROTECTED]> | [ 2002-10-24 21:48 +0200 ] > It does appear related to threads, based on the system calls in the > stack. You could try running it in single-process mode ( radiusd -s ) > to see if that avoids hitting a thread related problem.
I gave it a try by setting args -s -x -x from gdb and issueing a sighup. It crashed in the same way. :( (gdb) set args -s -xx (gdb) run Starting program: /usr/local/sbin/radiusd -s -xx [..] Program received signal SIGHUP, Hangup. 0x281139bc in _thread_sys_poll () from /usr/lib/libc_r.so.4 (gdb) (gdb) bt #0 0x281139bc in _thread_sys_poll () from /usr/lib/libc_r.so.4 #1 0x28112db8 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.4 #2 0x281126cf in _thread_kern_scheduler () from /usr/lib/libc_r.so.4 #3 0x0 in ?? () Thanks, Aragon - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
