FR 3.0.1 (radsec) crashes

JB list.freeradius at me.com
Thu Jan 30 20:17:24 CET 2014


Alan DeKok wrote:
>  Please pull the v3.0.x branch from github.  I've pushed a fix.
>  Alan DeKok.

With the newly built (with --prefix and --enable-developer) v3.0.x branch we're getting SEGFAULTS when an access point is turned off.
I've pasted logs and a GDB trace (not from the same occurrence).
Please let me know if you need further info from me.

Cheers,
JB


== Log 1 ==

FATAL SIGNAL: Segmentation fault
Backtrace of last 7 frames:
/usr/local/freeradius3/lib/libfreeradius-radius.so(+0x6d91) [0xb7712d91]
[0xb7767400]
/usr/local/freeradius3/sbin/radiusd() [0x807545e]
/usr/local/freeradius3/sbin/radiusd() [0x807596c]
/usr/local/freeradius3/sbin/radiusd() [0x8071ea9]
/lib/i386-linux-gnu/i686/cmov/libpthread.so.0(+0x5c39) [0xb74aac39]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(clone+0x5e) [0xb738b78e]
No panic action set
_EXIT CALLED src/lib/debug.c[262]: 1:

== Log 2 ==

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb5c35b70 (LWP 9824)]
0xb7cf9e03 in SSL_write () from /usr/lib/i386-linux-gnu/i686/cmov/libssl.so.1.0.0


== GDB ==

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb76a2b70 (LWP 9920)]
0x00000000 in ?? ()
#0  0x00000000 in ?? ()
No symbol table info available.
#1  0x080752ba in request_pre_handler (request=0x82b56c0, action=1) at src/main/process.c:1039
        rcode = -1217791151
#2  0x080758ce in request_running (request=0x82b56c0, action=1) at src/main/process.c:1234
        __FUNCTION__ = "request_running"
#3  0x08071ea9 in request_handler_thread (arg=0x8289648) at src/main/threads.c:696
        self = 0x8289648
#4  0xb7d24c39 in start_thread () from /lib/i386-linux-gnu/i686/cmov/libpthread.so.0
No symbol table info available.
#5  0xb7c0578e in clone () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
No symbol table info available.


More information about the Freeradius-Users mailing list