[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Assertion failure in ldapsearch

To: Michael Ströder <michael@stroeder.com>
Subject: Re: Assertion failure in ldapsearch
From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
Date: Sat, 22 Aug 2009 10:48:29 +0200
Cc: openldap-software@openldap.org
In-reply-to: <4A8F37E7.1060006@stroeder.com>
References: <4A8D77A2.60100@inria.fr> <4A8E374B.4010807@symas.com> <4A8E4907.1020402@inria.fr> <4A8F37E7.1060006@stroeder.com>
User-agent: Thunderbird 2.0.0.22 (X11/20090815)

Michael Ströder a écrit :

Guillaume Rousse wrote:

As 2.4.17 and 2.4.16 changelog doesn't show anything related, I guess
the pb is still there.


Please do not guess. You should test.

Unfortunatly, I have no way to reproduce the problem, and I couldn'tafford to let the ldap server in a bad mood. Isn't there any way toreplay answer parsing from the network capture ?

--
BOFH excuse #354:

Chewing gum on /dev/sd3c

Follow-Ups:
- Re: Assertion failure in ldapsearch
  - From: Aaron Richton <richton@nbcs.rutgers.edu>

References:
- Assertion failure in ldapsearch
  - From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
- Re: Assertion failure in ldapsearch
  - From: Howard Chu <hyc@symas.com>
- Re: Assertion failure in ldapsearch
  - From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
- Re: Assertion failure in ldapsearch
  - From: Michael Ströder <michael@stroeder.com>

Prev by Date: Re: Assertion failure in ldapsearch
Next by Date: tlsverifyclient security implications
Index(es):
- Chronological
- Thread