[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20060105: core file produced on sasquatch.tamu.edu

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.

  • Subject: 20060105: core file produced on sasquatch.tamu.edu
  • Date: Thu, 05 Jan 2006 16:06:19 -0700
>From: Unidata Support <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200512141423.jBEENY7s024151 LDM

Hi Steve,

I was poking around on sasquatch.tamu.edu when I noticed several
core files, some of which were quite large (>= 2GB).  I left the
latest core file created on January 3.

The strange thing about the core files is what 'file' has to say
about them.  For example:

file core.4381

core.4381: ELF 64-bit LSB core file AMD x86-64, version 1 (SYSV), SVR4-style, 
SVR4-style, from 'onf '

The 'onf ' appears to be the end of 'ldmd.conf'.  Why 'file' lists this
strange name is unknown.  Also strange is the output of the GNU debugger:

gdb core.4381 bin/rpc.ldmd
GNU gdb Red Hat Linux (6.3.0.0-1.63rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as 
"x86_64-redhat-linux-gnu"..."/usr/local/ldm/core.4381": not in executable 
format: File format not recognized

"/usr/local/ldm/bin/rpc.ldmd" is not a core dump: File format not recognized


I interpret this to mean that either the core file is completely hosed,
or gdb can not handle large core files.

Any ideas?

Cheers,

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.