RE: slapd segfaults on SuSe SLES 8.0(powered by UnitedLinux 3.0) (ITS#3175)

[ravishankar.srinivasan@hp.com]

Hi Kurt,

Here is the info :

(gdb) run -d 0
Starting program: /opt/openldap2.2/libexec/slapd -d 0
(no debugging symbols found)...[New Thread 1024 (LWP 3537)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 3537)]
0x00000000 in ?? ()
(gdb) bt full
#0  0x00000000 in ?? ()
No symbol table info available.
#1  0x08096ad3 in strcpy ()
No symbol table info available.
#2  0x080606f9 in strcpy ()
No symbol table info available.
#3  0x0804cf92 in strcpy ()
No symbol table info available.
#4  0x402244a2 in __libc_start_main () from /lib/libc.so.6
No symbol table info available.
(gdb)

I did build the package with debug option ON,but this is all the trace I
see..

Thanks
Ravi

-----Original Message-----
From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org] 
Sent: Wednesday, June 09, 2004 4:59 AM
To: SRINIVASAN, RAVISHANKAR
Cc: openldap-its@OpenLDAP.org
Subject: RE: slapd segfaults on SuSe SLES 8.0(powered by UnitedLinux
3.0) (ITS#3175)


At 06:50 AM 6/7/2004, ravishankar.srinivasan@hp.com wrote:
>Still no luck!here is the stack trace..

What you provide are log entries, not a stack trace.
See http://www.openldap.org/faq/index.cgi?file=59
for an overview of how to obtain a stack trace.

Kurt