Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!leah!rpi!batcomputer!cornell!rochester!rit!tropix!moscom!ur-valhalla!uhura.cc.rochester.edu!sunybcs!rutgers!cs.utexas.edu!tut.cis.ohio-state.edu!purdue!haven!h.cs.wvu.wvnet.edu!cerc.wvu.wvnet.edu!kannan@babcock.cerc.wvu.wvnet.edu
From: kannan@babcock.cerc.wvu.wvnet.edu (R. Kannan)
Newsgroups: comp.unix.questions
Subject: Re: What to do with core dumps?
Message-ID: <147@cerc.wvu.wvnet.edu.edu>
Date: 22 Jul 89 00:41:00 GMT
References: <4016@silver.bacs.indiana.edu>
Sender: news@cerc.wvu.wvnet.edu
Lines: 32

From article <4016@silver.bacs.indiana.edu>, by regoli@silver.bacs.indiana.edu (michael regoli):
> 
> what can you do with a core dump?  
> 
> when exiting from, say, a hung ftp session with ^\, what can you tell
> from the core file as to what happened and why?  how do you find out?

>   ...rutgers!iuvax!silver!regoli

there is a UNIX utility called "strings"

USAGE:

	strings core

Effect:

	Will output all printable characters from the file
        which here is the "core"

	Thus you can peek into the "core"
        and get some idea as to what happened.

PS: The fact that I have tried and played with "core" is a convincing proof
that I am not UNIX person yet. I am sure there are better things one
can do to find exactly what happened.

Thai is the reason core is created, I would think.



--kannan