Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!unmvax!deimos.cis.ksu.edu!uxc!tank!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.unix.questions
Subject: Re: What to do with core dumps?
Keywords: dumb question
Message-ID: <17582@mimsy.UUCP>
Date: 18 May 89 05:31:08 GMT
References: <4016@silver.bacs.indiana.edu>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 22

In article <4016@silver.bacs.indiana.edu> regoli@silver.bacs.indiana.edu
(michael regoli) writes:
>what can you do with a core dump?  

A core file contains the exact state of the process%, even including
such things as open file descriptors.  Given the program itself and
a symbol table (and a debugger), you can extract a stack trace,
examine variables, and do anything else the debugger can do.

>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?

Since ftp clients usually hang because the server to which they were
listening simply stops speaking, the core file usually tells you nothing
you did not already know.

-----
% Since this is unix.questions, not unix.wizards, we can ignore per-
  process state that appears only in the proc table not in u.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris