From owner-freebsd-current@FreeBSD.ORG Fri Jul 16 20:10:59 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1544D16A4CE; Fri, 16 Jul 2004 20:10:59 +0000 (GMT) Received: from ns1.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id E08C543D31; Fri, 16 Jul 2004 20:10:58 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from ns1.xcllnt.net (localhost [127.0.0.1]) by ns1.xcllnt.net (8.12.11/8.12.11) with ESMTP id i6GKAw4V007967; Fri, 16 Jul 2004 13:10:58 -0700 (PDT) (envelope-from marcel@ns1.xcllnt.net) Received: (from marcel@localhost) by ns1.xcllnt.net (8.12.11/8.12.11/Submit) id i6GKAwCo007966; Fri, 16 Jul 2004 13:10:58 -0700 (PDT) (envelope-from marcel) Date: Fri, 16 Jul 2004 13:10:58 -0700 From: Marcel Moolenaar To: Willem Jan Withagen Message-ID: <20040716201058.GD7534@ns1.xcllnt.net> References: <0b8301c46b52$96931b50$471b3dd4@digiware.nl> <0bec01c46b5a$98469e10$471b3dd4@digiware.nl> <20040716183406.GA7534@ns1.xcllnt.net> <0c0801c46b6c$94f54b00$471b3dd4@digiware.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0c0801c46b6c$94f54b00$471b3dd4@digiware.nl> User-Agent: Mutt/1.5.5.1i cc: freebsd-current@freebsd.org cc: Robert Watson Subject: Re: One more ..... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jul 2004 20:10:59 -0000 On Fri, Jul 16, 2004 at 09:39:16PM +0200, Willem Jan Withagen wrote: > From: "Marcel Moolenaar" > > 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. That's all good, and normally this gives you DDB as the default debugger backend. Typically if you only see "KDB: enter: panic", then KDB is using the GDB backend. Hmmm... It may be a good idea to tell people that. Somthing like: KDB: entering ddb: panic or KDB: entering gdb: bootflags requested debugger -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net