Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site pur-ee.UUCP
Path: utzoo!linus!security!genrad!grkermit!masscomp!clyde!ihnp4!inuxc!pur-ee!notes
From: notes@pur-ee.UUCP
Newsgroups: net.unix-wizards
Subject: 'core' & stack traces - (nf)
Message-ID: <1149@pur-ee.UUCP>
Date: Thu, 24-Nov-83 22:32:10 EST
Article-I.D.: pur-ee.1149
Posted: Thu Nov 24 22:32:10 1983
Date-Received: Sat, 26-Nov-83 06:45:02 EST
Sender: notes@pur-ee.UUCP
Organization: Electrical Engineering Department , Purdue University
Lines: 34

#N:ecn-ee:13000001:000:783
ecn-ee!davy    Nov 24 22:17:00 1983


Two things:

	1) Has anybody got a program which prints a stack trace of
	   a program given a.out and core?  I KNOW "sdb" will do it,
	   but sdb doesn't work on 4.2 BSD.

	   I'm looking for something that prints output like:

		program died on line XXX of YYY.c:
			<program source code line>

		stack trace of program:

			foo(123, 456, 789) [YYY.c:XXX]
			bar(10) [YYY.c:ZZZ]
			goo() [YYY.c:AAA]
			main(1234567, 98765433, 3242) [YYY.c:BBB]
	
	2) Can anybody explain to me EXACTLY what a "core" file looks
	   like?  I know it's got a user structure, the user area, and
	   the data + stack segments, but that's all I've been able to
	   find in the documentation.  How do you interpret all the
	   crap that's in there?  

--Dave Curry
decvax!pur-ee!davy
eevax.davy@purdue