Try running with LD_ASSUME_KERNEL=2.4.19. This will force runtime linking against the standard libc libs instead of the thread-local storage (tls) libs. So, on the command line, run "LD_ASSUME_KERNEL=2.4.19 radiusd -X" and see if that segfaults.

--Mike

Alan DeKok wrote:
Daniel J McDonald <[EMAIL PROTECTED]> wrote:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1076829024 (LWP 17140)]
0x40079e54 in pthread_mutex_lock () from /lib/tls/libpthread.so.0
(gdb) bt
#0  0x40079e54 in pthread_mutex_lock () from /lib/tls/libpthread.so.0
#1  0x406215dd in ldap_pvt_thread_mutex_lock ()
from /usr/lib/libldap_r.so.2
#2  0x40628443 in ldap_pvt_sasl_mutex_lock ()
from /usr/lib/libldap_r.so.2
#3  0x4042028e in sasl_dispose () from /usr/lib/libsasl2.so.2


  Sounds like a library conflict to me.  I'm not sure what to suggest...

  Alan DEKok.

- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to