Hallvard B Furuseth wrote:
masarati(a)aero.polimi.it writes:
> Not sure whether it is related, but I'm currently running test036 with
> -DLDAP_THREAD_DEBUG (for unrelated purposes) and I see some mutex-related
> failures, of the type
>
> conn=1031 op=1 SRCH base="cn=Monitor" scope=2 deref=0
filter="(objectClass=*)"
> ../../../ldap-2.4-src/libraries/libldap_r/thr_debug.c:1029:
> ldap_pvt_thread_mutex_unlock error: !THREAD_MUTEX_OWNER( mutex )
Got a backtace?
No (I was using LDAP_THREAD_DEBUG=noabort).
And maybe valgrind output with
env LDAP_THREAD_DEBUG=alloc,nosync ./run test036?
Yes, but lost and unable to reproduce so far, sorry. At first I thought
it was easily reproducible, so I didn't try that hard; eventually I was
unable to reproduce using regular slapd. It occurred running slapd
under valgrind and a certain combination of of -S/-SS in slapd-tester.
Later I'll try to reproduce the right combination of parameters.
p.