Segmentation fault in OpenLDAP 2.1.25

[John Borwick <borwicjh@wfu.edu>]

Hello.  I hope you are all doing well.

When I query an 'ldap' backend that aliases to a BDB backend on the same 
server (running OpenLDAP 2.1.25, the stable release), slapd exits with a 
segmentation fault.  The ldapsearch query sees

ldapsearch -b 'o=WFU,c=US' -x
[...]
ldap_result: Can't contact LDAP server (81)

and the slapd process dies.  slapd says it segfaults when you run it in 
the foreground.  The last few lines are

--last part of 'slapd -d -1'--
ldap_chase_referrals
read1msg:  V2 referral chased, mark request completed, id = 2
new result:  res_errno: 32, res_error: <>, res_matched: <>
read1msg:  0 new referrals
read1msg:  mark request completed, id = 2
request 2 done
res_errno: 32, res_error: <>, res_matched: <>
ldap_free_request (origid 2, msgid 2)
ldap_free_connection
ldap_free_connection: refcnt 1
ldap_parse_result
ber_scanf fmt ({iaa) ber:
ber_dump: buf=0x08207820 ptr=0x08207823 end=0x0820782c len=9
  0000:  65 07 0a 01 20 04 00 04  00                        e... .... 

ber_scanf fmt (}) ber:
ber_dump: buf=0x08207820 ptr=0x0820782c end=0x0820782c len=0

ldap_msgfree
daemon: select: listen=6 active_threads=1 tvp=NULL
--end 'slapd -d -1'--

My amateur take on the log is that the failure is somewhere between the 
query resolution on the BDB backend and the translation back through the 
ldap backend.

slapd.conf's configuration for o=WFU,c=US looks like

# the 'fake' database, for legacy clients
database        ldap
suffix          "o=WFU,c=US"
uri             ldap://localhost
suffixmassage   o=WFU,c=US      ou=Users,dc=wfu,dc=edu


I have put extensive information up at 
http://www.wfu.edu/~borwicjh/examples/openldap-2.1.25-segfault/ , 
including my slapd.conf , the output of 'slapd -d -1', and the relevant 
local4.* information from syslog.

The twist is, I installed OpenLDAP 2.1.25 from an RPM I created for 
internal use.  The spec file for that RPM is available on the 
above-mentioned website, too.  I'm building the RPM on the same OS I'm 
deploying it on: Red Hat Enterprise 3.0.  (I'm creating an RPM for 
2.1.25 so I don't have to use Red Hat's OpenLDAP 2.0 RPM.)

Relevant information from the spec file:

%configure \
	--enable-ldap \
	--libexecdir=%{_sbindir} \
        --localstatedir=/%{_var}/run

(All that's being turned on is the ldap backend.)

Does anyone know what's going on?

Thanks!
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
John Borwick, Systems Infrastructure
Wake Forest University

Attachment: signature.asc
Description: OpenPGP digital signature