From owner-freebsd-bugs  Mon Sep 29 20:51:43 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id UAA29233
          for bugs-outgoing; Mon, 29 Sep 1997 20:51:43 -0700 (PDT)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA29227
          for <freebsd-bugs@FreeBSD.ORG>; Mon, 29 Sep 1997 20:51:39 -0700 (PDT)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id UAA09399;
	Mon, 29 Sep 1997 20:51:52 -0700 (PDT)
Message-Id: <199709300351.UAA09399@implode.root.com>
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
cc: freebsd-bugs@FreeBSD.ORG
Subject: Re: kern/4630: buffer_map might become corrupted 
In-reply-to: Your message of "Mon, 29 Sep 1997 22:17:41 +0200."
             <1391.875564261@critter.freebsd.dk> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Mon, 29 Sep 1997 20:51:52 -0700
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 ?

   That's what I meant if it wasn't clear - yes, you'd only save the summary.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project