From owner-freebsd-current  Tue May 14 05:51:00 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id FAA06227
          for current-outgoing; Tue, 14 May 1996 05:51:00 -0700 (PDT)
Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA06219
          for <current@freebsd.org>; Tue, 14 May 1996 05:50:57 -0700 (PDT)
Received: from allegro.lemis.de by diablo.ppp.de with smtp
	(Smail3.1.28.1 #1) id m0uJJYi-000QYMC; Tue, 14 May 96 14:50 MET DST
From: grog@lemis.de (Greg Lehey)
Organisation: LEMIS, Schellnhausen 2, 36325 Feldatal, Germany
Phone: +49-6637-919123
Fax:   +49-6637-919122
Received: (grog@localhost) by allegro.lemis.de (8.6.9/8.6.9) 
	id OAA11589 for current@freebsd.org; Tue, 14 May 1996 14:40:44 +0200
Message-Id: <199605141240.OAA11589@allegro.lemis.de>
Subject: ktrace still not working?
To: current@freebsd.org
Date: Tue, 14 May 1996 14:40:44 +0200 (MET DST)
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I thought ktrace was fixed, but today I had a panic after using
ktrace.  It screwed things up so completely that I couldn't even take
a dump, but if I recall correctly it was an address trap out of
free(), called via some ffs_ function from ktr_syscall or some such.
If it happens again, can anybody give me an idea of what to look for
in ddb (apart from the obvious stack trace)?

Greg