This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Tyler, >Date: Thu, 4 Aug 2005 15:46:17 -0400 (EDT) >From: "Tyler Allison" <address@hidden> >Organization: allison.com >To: "Steve Emmerson" <address@hidden> >Subject: Re: LDM 6.4.1 segfault The above message contained the following: > Okay. Had another seg fault. I believe I had some kind of network issue > right before the crash which may be tickling some kind of bug. Note the > disconnects and reconnects (flapping). > > Logs before the crash are attached. > > What would you like me to do to help you debug this? > I'm a slightly above average sysadmin, but it's not a full time job, so be > specific if you can. > > No core was dropped that I can find. > > - Base Linux is Centos 3.4 (final) > - gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-49) > gcc Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=x86_64-redhat-linux > - Stock/RPM kernel kernel-2.6.10dn-1 Try the following: 1. Go to the top-level LDM source-directory. 2. Execute the command "make distclean" 3. Set the environment variable CFLAGS to "-g" (without the quotes). 4. Rebuild the LDM package. 5. Stop the LDM. 6. Reinstall the LDM package. 7. Ensure that core dumps are allowed, e.g., ulimit -c unlimited The exact form depends on your user-shell. 8. Start the LDM. Regards, Steve Emmerson