> make install With 2.3, you need to set STRIP='' on the 'make install'. Otherwise the -g is undone by the "make install" (as appears to be this case). You can rerun 'make install' safely (with STRIP reset) if you still have your source tree around.
> Reading symbols from /usr/local/lib/libdb-4.3.so...(no debugging symbols > found)...done. It's a lot easier to read a trace if everything (in this case SleepyCat) is compiled '-g'. > Reading symbols from /usr/lib/libssl.so.3...(no debugging symbols > found)...done. "Everything compiled -g" also applies to vendor/distribution-supplied libraries. You should contact your vendor to figure out how to get them. > No symbol table info available. So long as you're getting significant numbers of "no debugging symbols found"/"No symbol table info available," the core dumps are going to be nearly incomprehensible to developers. Keep playing with your reproduction environment until you get there. To give you an idea of where you're headed, Samuel Tran's message from yesterday (http://www.openldap.org/lists/openldap-software/200508/msg00155.html) included a usable gdb backtrace. Notice the lack of "in ??" lines.
