From owner-freebsd-new-bus Tue Jun 27 3:50:54 2000 Delivered-To: freebsd-new-bus@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id D195437B7E3 for ; Tue, 27 Jun 2000 03:50:49 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id UAA00083; Tue, 27 Jun 2000 20:50:33 +1000 Date: Tue, 27 Jun 2000 20:50:30 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Warner Losh Cc: new-bus@FreeBSD.ORG Subject: Re: Debugger vs panic In-Reply-To: <200006270322.VAA30153@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-new-bus@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 26 Jun 2000, Warner Losh wrote: > There's lots of places in newbus that programming errors trigger a > panic. This can make it very difficult to debug the probe/attach > routines. Is there any way that this can just dump you into the > debugger and then return out failing the call? Not in general. Code that calls panic() is generally not prepared for panic() to return. Apart from that, you can add a call to Debugger() near the start of panic(), and sometimes return from panic(). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-new-bus" in the body of the message