From owner-freebsd-hackers Thu Mar 7 06:51:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA12084 for hackers-outgoing; Thu, 7 Mar 1996 06:51:25 -0800 (PST) Received: from bacall.lodgenet.com ([205.138.147.242]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA12072 for ; Thu, 7 Mar 1996 06:51:19 -0800 (PST) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id IAA07088 for ; Thu, 7 Mar 1996 08:45:05 -0600 Received: from tserv.lodgenet.com(204.124.120.10) by bacall via smap (V1.3) id sma007074; Thu Mar 7 08:45:05 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by tserv.lodgenet.com (8.6.12/8.6.12) with ESMTP id IAA01201; Thu, 7 Mar 1996 08:12:41 -0600 Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.7.4/8.6.12) with SMTP id IAA16678; Thu, 7 Mar 1996 08:24:56 -0600 (CST) Message-Id: <199603071424.IAA16678@jake.lodgenet.com> X-Authentication-Warning: jake.lodgenet.com: Host localhost [127.0.0.1] didn't use HELO protocol X-Mailer: exmh version 1.6.2 7/18/95 To: Greg Lehey cc: davidg@Root.COM, hackers@FreeBSD.ORG (Hackers; FreeBSD) Subject: Re: using ddb to debug a double-panic? In-reply-to: Your message of "Thu, 07 Mar 1996 11:01:51 +0700." <199603071005.LAA20629@nixpbe.pdb.sni.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Mar 1996 08:24:56 -0600 From: "Eric L. Hernes" Sender: owner-hackers@FreeBSD.ORG Precedence: bulk I've been thinking about it too, but for now it's quite useable and that's the important thing. > > I've been thinking about improving ddb. About 4 years ago, I wrote a > similar kernel debugger for BSD/386, and was thinking of incorporating > some of its features into ddb. One of the things it could do was > exactly this kind of stack trace (well, it supplied other information > as well). I won't get round to doing it until May, though. > > Does anybody else have ideas about improving ddb? > yea, SCO's kernel debugger has a few more advanced features that I kind of like, that probably wouldn't be too hard to implement: a readline type history, macros and user-defined functions, casting and structure dumping (maybe done through macros), watchpoints (do these work in ddb?), the single step execution holds your hand a bit better, and a couple others. I'd also like to be able to load in a new symbol table, such as when an lkm is loaded. Now it's only possible to debug loaded lkms, by running nm on the module_mod output from the modload, and using the addresses from that. I realize that this opens a can of worms wrt to multiple lkms and unloading, but usually you've gotta reboot before that'd kill you anyhow :). Maybe there's a better way to do this too. > Greg > > eric. -- erich@lodgenet.com erich@rrnet.com