Thanks Chris

But openldap-2.4.23 is the current stable release, or did I miss something?

-----Original Message-----
From: Chris Jacobs <Chris.Jacobs@apollogrp.edu>
To: Aaron Richton <richton@nbcs.rutgers.edu>, Yusuf Rajah <yusuf@josephking.it>
Cc: openldap-technical@openldap.org <openldap-technical@openldap.org>
Subject: RE: openldap-2.4.23 Segfault with Error number: 0xffffffffffffffff ()
Date: Tue, 24 Aug 2010 11:37:03 -0700

And you're also probably going to be told to upgrade.  Support for previous versions tends to start with 'use the newer version'.  Fyi...

- chris

-----Original Message-----
From: openldap-technical-bounces@OpenLDAP.org [mailto:openldap-technical-bounces@OpenLDAP.org] On Behalf Of Aaron Richton
Sent: Tuesday, August 24, 2010 8:05 AM
To: Yusuf Rajah
Cc: openldap-technical@openldap.org
Subject: Re: openldap-2.4.23 Segfault with Error number: 0xffffffffffffffff ()

On Tue, 24 Aug 2010, Yusuf Rajah wrote:

> Aug 24 15:45:24 sms kernel: [ 3368.265357] slapd[1437]: segfault at 28 ip 00000000004aa995 sp 00007f5b9b78ac10 error 4 in slapd[400000+169000]
>
> I am not sure how to tackle this, your pearls of wisdom will be tremendously appreciated.

You're probably going to want to report this formally (to the OpenLDAP
ITS) once you get a bit more information;
http://www.openldap.org/faq/data/cache/59.html describes the information
requested. You're going to want a full backtrace at a minimum; this is
somewhat dependent on your exact environment as you'll need to make sure
that you have unstripped binaries and/or debug packages and/or appropriate
ulimits and similar.


This message is private and confidential. If you have received it in error, please notify the sender and remove it from your system.