Subject: Re: Source code changes... Kernel stability
To: Robert L. Shady <>
From: Chris G. Demetriou <cgd@postgres.Berkeley.EDU>
List: current-users
Date: 05/05/1994 15:18:32
> Speaking of which, I never got an answer to my question about tracing a
> kernel panic.  Do you have a "quick-n-dirty" way of finding out what
> module/routine caused it and possibly dump the variables, or something?

in DDB, "trace" (funny name for it, eh?  8-) will do what you want.
as for dumping the variables, well, DDB isn't quite that
sophisticated (it will show you arguments, though, if you know what
you're looking for).  i'd get out the source to the routine, the assembler
version of the routine, etc., and spend time digging...

> Cute.. I was just hoping you weren't going to say one from yesterday, cause
> I just removed it.. ;)  I think I will re-sup the current-src portion just
> to make sure I have "the right stuff" because I haven't been able to sup
> everyday for a while now...  What SUP lists are available?  I currently
> have...

those should get you what you need; most of the rest of the 'current'
releases are subsets of allsrc.