SPUG: Core files....
storer at bcstec.ca.boeing.com
Wed Sep 29 12:50:38 CDT 1999
> ...every once in a while it just
> randomly quits and dumps a core. I don't get any other error message, it
> just says "Segmentation fault (core dumped)"
I've seen this behavior when a Solaris machine has used up all its physical and
virtual memory. I checked Sun's online documentation and found this:
Segmentation faults usually result from programming error. This message is usually
accompanied by a core dump, except on read-only filesystems.
To see which program produced a core file, run either the file(1) command or
the adb(1) command. The following examples show the output of the file and adb
commands on a core file from the dtmail program.
$ file core
core: ELF 32-bit MSB core file SPARC Version 1, from 'dtmail'
$ adb core
core file = core P program'dtmail' SIGSEGV 11: segmentation violation
^D (use Control-d to quit the adb rogram)
Ask the vendor or author of this program for a debugged version.
A process has received a signal indicating that it attempted to access an area of
memory that is protected or that does not exist. The two most common causes of
segmentation faults are attempting to dereference a null pointer or indexing past
the bounds of an array.
(From the "Solaris Common Messages and Troubleshooting Guide" online at
http://docs.sun.com:80, found in the Sys Admin AnswerBook Collection Vol 2
for Solaris 2.6)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
POST TO: spug-list at pm.org PROBLEMS: owner-spug-list at pm.org
Seattle Perl Users Group (SPUG) Home Page: http://www.halcyon.com/spug/
SUBSCRIBE/UNSUBSCRIBE: Replace ACTION below by subscribe or unsubscribe
Email to majordomo at pm.org: ACTION spug-list your_address
More information about the spug-list