From owner-freebsd-current Wed Jun 23 18:11:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 4A6DF15144 for ; Wed, 23 Jun 1999 18:11:30 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id SAA09476; Wed, 23 Jun 1999 18:11:21 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Wed, 23 Jun 1999 18:11:21 -0700 (PDT) From: Doug X-Sender: doug@dt054n86.san.rr.com To: Greg Lehey Cc: Doug , freebsd-current@FreeBSD.ORG Subject: Re: ktrace causes kernel panic In-Reply-To: <19990624100825.G417@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 24 Jun 1999, Greg Lehey wrote: > On Wednesday, 23 June 1999 at 11:45:12 -0700, Doug wrote: > > Using a recent (few days) -current I had a process lock up on me > > last night, so I did a 'ktrace -p whateverthepidwas' and let it run for a > > while. When I issued a 'ktrace -C' in another screen, everything froze and > > the kernel panic'ed. I dropped to the debugger on the console and it was > > definintely ktrace that caused the panic. > > So where's the dump? A stack trace would be informative. Sorry, forgot to mention that I didn't have time to write down the trace because the boss was breathing down my neck to get the thing back on line. I remember distinctly that the second to last function was ktrace() if that's any help. Doug -- On account of being a democracy and run by the people, we are the only nation in the world that has to keep a government four years, no matter what it does. -- Will Rogers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message