Re: POSIX_THREADS segfaulting (ITS#11)

[alan_k@HK.Super.NET]

Right,

Replying to the 'its' address this time :)

This is the backtrace after compliling with --without-threads
- from my reading of the code though, even though it is not a threaded
application, it emulates the calls (not sure if that at all relivant,
but at least I tried :-)

end of -d1 output, then info stack

I've got some more probs with select gdbm database - I'll post that as a
seperate issue to 'its' 

regards
alan

<= filter_candidates 0
=> filter_candidates
=> ava_candidates 0xa3
=> index_read( "member" "=" "CN=PERSON ALAN KNOWLES, O=ENVISION
INTEGRATED DESIGN CONSULTANCY, OU=CONTACTS, O=OSSC, C=HK" )
=> ldbm_cache_open( "/usr/tmp/member.dbb", 66, 600 )
<= ldbm_cache_open (opened 4)
<= index_read 0 candidates
<= ava_candidates 0
<= filter_candidates 0
<= list_candidates 0
<= filter_candidates 0
send_ldap_result 0:H:

Program received signal SIGSEGV, Segmentation fault.
0x4009acc8 in free ()
(xxgdb) info stack
#0  0x4009acc8 in free ()
#1  0x4009ac71 in free ()
#2  0x80586d2 in ber_free (ber=0x400efe80, freebuf=1) at io.c:262
#3  0x8050175 in op_free (op=0x806fc88) at operation.c:17
#4  0x80502ab in op_delete (olist=0x8070178, op=0x806fc88) at
operation.c:74
#5  0x804af29 in connection_operation (arg_v=0x8084420) at
connection.c:92
#6  0x80616bc in pthread_create (tid=0x806fcb4, attr=0xbffffa24,
func=0x804aca0 <connection_operation>, arg=0x8084420) at thread.c:522
#7  0x804b247 in connection_activity (conn=0x8070114) at
connection.c:201
#8  0x804aad4 in slapd_daemon (port=0x185) at daemon.c:362
#9  0x80616bc in pthread_create (tid=0x806c7a0, attr=0xbffffcd0,
func=0x8049e20 <slapd_daemon>, arg=0x185) at thread.c:522