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

Re: Ldapsearch causing Seg Fault

Sorry about the delay, the details are as follows (see below).

On Tue, 20 Apr 1999, Kurt D. Zeilenga wrote:

> At 03:35 PM 4/20/99 +0100, D J Richards wrote:
> >
> >Hi all,
> >
> >I've just installed the stable release (1.2.1) successfully under Solaris
> >2.5.1.
> >
> >All the tests executed correctly and I have been able to setup a simple
> >directory.
> >
> >However, this is where things get interesting. I can run ldapsearch
> >without any problems and it returns the expected results, however, if I
> >run ldapsearch with the -v switch, it causes a Segmentation Fault (and
> >returns no other info).
> Can you provide details?  Are you using --without-threads,
> --with-thread=posix, or --with-threads=lwp?  Which backend are
> you using?  If LDBM, which underlying database manager?  Are you
> using non-vendor tools and libraries?
The build was as follows:
setenv LIBS "-pthread -lposix4";
env CPPFLAGS="-I/path/to/db2/include" LDFLAGS="-L/path/to/db2/lib" \
configure --with-threads=lwp --prefix=/path/to/openldap

I'm using the LDBM backend with Sleepycat's DB2 DBMS. I'm not using any
other tools/libraries not suplied with the openldap release.

> Did ldapsearch seg fault or was it slapd?  Can you provide a
> backtrace from the core dump?  Also, what's the tail of the
> log file look like?
ldapsearch caused te seg fault, the slpad daemon continued to work
perfectly -- and accepted non-verbose searches. If you are referring to
the system log files then I don't have access to them (I can find any
slapd specific log files) and I wouldn't know
where to start with the core dump.

--- Dan