From owner-freebsd-bugs Mon Sep 29 13:19:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA05956 for bugs-outgoing; Mon, 29 Sep 1997 13:19:17 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA05937 for ; Mon, 29 Sep 1997 13:19:10 -0700 (PDT) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id WAA01393; Mon, 29 Sep 1997 22:17:41 +0200 (CEST) To: dg@root.com cc: Bob Bishop , freebsd-bugs@FreeBSD.ORG Subject: Re: kern/4630: buffer_map might become corrupted In-reply-to: Your message of "Mon, 29 Sep 1997 12:14:58 PDT." <199709291914.MAA06285@implode.root.com> Date: Mon, 29 Sep 1997 22:17:41 +0200 Message-ID: <1391.875564261@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199709291914.MAA06285@implode.root.com>, David Greenman writes: >>Isn't that just a (k)gdb script in a wrapper, run after savecore has done >>its thing? > > kgdb scripting is painfully slow, difficult to write, and not very >flexible. What I'd like to see is a cda that is built along with the kernel >so it's data structures are correct and it stays in sync with the kernel >sources. I'd also like the utility to be able to read the crash dump saved >in swap without having to copy it first to a file (since few people have >the space for large crash dump images). maybe make a "dump-light" thing ? Instead of dumping all the stuff, it merely prints a traceback + various other info and stores that as the crashdump ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop."