[Date Prev][Date Next]
Re: (ITS#4924) assertion failure during test039-glue-ldap-concurrency
On Thursday 12 April 2007 12:01, Pierangelo Masarati wrote:
> firstname.lastname@example.org wrote:
> > email@example.com wrote:
> >> I was able to reproduce this problem again. It does not happen during
> >> every run of test039-glue-ldap-concurrency (probably during 1 out of
> >> 10). This time I had enabled debug logging in the slapd-search tester.
> >> Find the log of it below. What's really strange that it fails when
> >> chasing a referral to ldap://localhost:9016 (there is nothing listening
> >> on port 9016 during test039)
> >> ldap_new_connection 0x100141e0: unexpected response 96 from BIND request
> >> id=376 lt-slapd-search: request.c:470: ldap_new_connection: Assertion
> >> `0' failed.
> > 96 is LDAP_REQ_BIND, which __should_not__ be returned by ldap_result()
> > in any case. The bug is buried deeper in libldap, so the assert(0) was
> > apparently worth :)
> Another comment: would it be possible to check if the problem was
> already present in earlier versions?
Yes, I had that on my list already. I am also trying to reproduce it on a
different architecture, currently I only used different PowerPC machines.