Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 4 May 2012 13:33:24 GMT
From:      Oliver Hartmann <ohartman@zedat.fu-berlin.de>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   ports/167576: net/openldap24-server
Message-ID:  <201205041333.q44DXOZu000376@red.freebsd.org>
Resent-Message-ID: <201205041340.q44DeASF015783@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         167576
>Category:       ports
>Synopsis:       net/openldap24-server
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri May 04 13:40:10 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator:     Oliver Hartmann
>Release:        FreeBSD 10-CURRENT/amd64 r234997
>Organization:
FU Berlin
>Environment:
>Description:
OpenLDAP 2.4.31 crashes on most recent FreeBSD 10.0-CURRENT r234997.

Compiled with CLANG, it core dumps immediately after starting slapd. Compiled with legcy gcc 4.2.1, the server slapd starts as usual, but any attempt to contact the server (id USERNAME, for instance) makes slapd Segmentation faulting as when compiled with CLANG, when the coredump occurs immediately.

A further investigation is impossible at the moment, since FreeBSD 10 systems are mostly down.
>How-To-Repeat:
Update FreeBSD 10.0-CURRENT/amd to r234997. Have a OpenLDAP backed environment as usual in larger server environments and have OpenLDAP 2.4.31 SASL server slapd running. Watch slapd dying and making your network stuck. 
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201205041333.q44DXOZu000376>