*BSD News Article 74397


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!oleane!jussieu.fr!math.ohio-state.edu!howland.reston.ans.net!gatech!usceast!tupelo!kbrown
From: kbrown@tupelo.sc.edu (Kevin Brown)
Newsgroups: comp.unix.bsd.netbsd.misc
Subject: How to make DDB dump core
Date: 15 Jul 1996 21:04:34 GMT
Organization: University of South Carolina - Columbia - Computer Science
Lines: 33
Message-ID: <4sebp2$fhj@redwood.cs.sc.edu>
NNTP-Posting-Host: tupelo.cs.sc.edu
X-Newsreader: TIN [version 1.2 PL2]

The changes I've added to the TCP code in NetBSD cause it to crash (of
course).  This I don't mind.  However, I've compiled in DDB which
catches the panic (which is useful).  I cannot get DDB to dump core
though so that I can later use kgdb to analyze the crashdump.

I've looked at the FreeBSD site which suggests typing either:

db> call diediedie()
or
db> call panic()

both of these give this response:

Faulted in DDB, continuing

So I've got to call cpu-reset() which gives me no crashdump.

I'm running NetBSD 1.1 on a pentium 100MHz, 32MB RAM.

On a related note, I think I made the swap partition too small (just
over 32 MB) - which seems to be keeping the crash dump from working
correctly even when DDB is not configured.  Is it possible to use a
crash file like L*n*x does?

Any advice much appreciated.  Thanks in advance.

--
-- 

Kevin Brown
Department of Computer Science	       email: kbrown@cs.scarolina.edu
University of South Carolina	       http://www.cs.sc.edu/~kbrown
Columbia SC 29208 	               (803) 777-1710