Date: Fri, 16 Jul 2004 21:39:16 +0200 From: "Willem Jan Withagen" <wjw@withagen.nl> To: "Marcel Moolenaar" <marcel@xcllnt.net> Cc: Robert Watson <rwatson@freebsd.org> Subject: Re: One more ..... Message-ID: <0c0801c46b6c$94f54b00$471b3dd4@digiware.nl> References: <Pine.NEB.3.96L.1040716121933.4361A-100000@fledge.watson.org> <0b8301c46b52$96931b50$471b3dd4@digiware.nl> <0bec01c46b5a$98469e10$471b3dd4@digiware.nl> <20040716183406.GA7534@ns1.xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
From: "Marcel Moolenaar" <marcel@xcllnt.net> > On Fri, Jul 16, 2004 at 07:30:31PM +0200, Willem Jan Withagen wrote: > > > > panic: process 82471(sh):2 holds Giant but isn't blocked on a lock > > > > cpuid = 1; > > KDB: enter: panic > > > > Is there any purpose in reporting these crashes this way??? > > You might want to make sure your debugger backend is DDB and not > GDB. This is what I have: # Debugging for use in -current options KDB # Enable kernel debugger support. options KDB_TRACE options DDB # Support DDB. options GDB # Support remote GDB. options INVARIANTS # Enable calls of extra sanity checking options INVARIANT_SUPPORT # Extra sanity checks of internal struct ures, required by INVARIANTS options WITNESS # Enable checks to detect deadlocks and cycles options WITNESS_SKIPSPIN # Don't run witness on spinlocks for spe ed Next to having an SMP/Opteron system. --WjW
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0c0801c46b6c$94f54b00$471b3dd4>