Date: Tue, 1 Apr 1997 08:29:56 +0200
From: j@uriah.heep.sax.de (J Wunsch)
To: dbx@atmos.washington.edu ("Doug Burks")
Cc: bugs@freebsd.org, toor@dyson.iquest.net (John S. Dyson)
Subject: Re: kern/3156: Floppy disk copy freezes
Message-ID: <19970401082956.CG29737@uriah.heep.sax.de>
In-Reply-To: <Pine.NEB.3.95q.970331150917.8703A-100000@cargpc5.atmos.washington.edu>; from "Doug Burks" on Mar 31, 1997 15:11:43 -0800
References: <19970331220620.KM38633@uriah.heep.sax.de> <Pine.NEB.3.95q.970331150917.8703A-100000@cargpc5.atmos.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
As "Doug Burks" wrote: > Can i convince you to compile a kernel with DDB, ... > Can do, though it may take me a few days before I can get around to do > so. Is breaking into DDB documented somewhere? If I do break in, is > there anything specific you want me to look for and/or retrieve? The debugger hotkey used to be Ctrl-Alt-ESC, but i think some (all?) syscons keymaps define it to Ctrl-PrtScr now. Using DDB is documented in the section about kernel debugging in the handbook. I'm not sure whether John has some questions to you, but for sure it would be at least interesting to see if the machine is still alive, and which processes are running (and in which state they are). DDB has a builtin ps command resembling ps(1). Also, if you happen to break it inside the kernel code (as opposed to inside the CPU idle loop), a stack trace will be interesting. You might even try sending a signal to a process. Use the address of the proc structure as displayed by DDB's ps command, and say: call psignal(<addr>, 9) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970401082956.CG29737>