Martin Husemann wrote:

>On Wed, Sep 21, 2005 at 11:48:14AM -0400, Jean-Luc Wasmer wrote:
>  
>
>>so I guess it's a pthread issue in current.
>>    
>>
>
>No, it's a bug in the application. Can you attach gdb and make it crash
>then? The backtrace will tell you which mutex it is.
>  
>
Program received signal SIGABRT, Aborted.
[Switching to LWP 1]
0xbd86071b in kill () from /usr/lib/libc.so.12
(gdb) backtrace
#0  0xbd86071b in kill () from /usr/lib/libc.so.12
#1  0xbd91c009 in pthread__errorfunc () from /usr/lib/libpthread.so.0
#2  0xbd919047 in pthread_mutex_unlock () from /usr/lib/libpthread.so.0
#3  0xbd965e6f in apr_thread_mutex_unlock () from /usr/pkg/lib/libapr-0.so.0
#4  0xbd964eb5 in apr_global_mutex_unlock () from /usr/pkg/lib/libapr-0.so.0
#5  0x0806c656 in util_ldap_cache_checkuserid ()
#6  0x0806f27a in mod_auth_ldap_check_user_id ()
#7  0x080e1e8c in ap_run_check_user_id ()
#8  0x080e27d2 in ap_process_request_internal ()
#9  0x080a131d in ap_process_request ()
#10 0x0809cac1 in ap_process_http_connection ()
#11 0x080d628c in ap_run_process_connection ()
#12 0x080d65a1 in ap_process_connection ()
#13 0x080ca34f in child_main ()
#14 0x080ca510 in make_child ()
#15 0x080ca57d in startup_children ()
#16 0x080cad23 in ap_mpm_run ()
#17 0x080d07f7 in main ()
#18 0x08066e56 in ___start ()


Jean-Luc