Date: Thu, 24 Jun 1999 10:45:02 +0930 From: Greg Lehey <grog@lemis.com> To: Doug <Doug@gorean.org> Cc: freebsd-current@FreeBSD.ORG Subject: Re: ktrace causes kernel panic Message-ID: <19990624104502.N417@freebie.lemis.com> In-Reply-To: <Pine.BSF.4.05.9906231809480.9469-100000@dt054n86.san.rr.com>; from Doug on Wed, Jun 23, 1999 at 06:11:21PM -0700 References: <19990624100825.G417@freebie.lemis.com> <Pine.BSF.4.05.9906231809480.9469-100000@dt054n86.san.rr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, 23 June 1999 at 18:11:21 -0700, Doug wrote: > 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. Not much. You'll need to get a dump. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990624104502.N417>