From owner-freebsd-new-bus Wed Jun 28 9:34:53 2000 Delivered-To: freebsd-new-bus@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6754237BD5D for ; Wed, 28 Jun 2000 09:34:50 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA80225; Wed, 28 Jun 2000 10:34:48 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA56222; Wed, 28 Jun 2000 10:34:46 -0600 (MDT) Message-Id: <200006281634.KAA56222@harmony.village.org> To: Nick Hibma Subject: Re: Debugger vs panic Cc: new-bus@freebsd.org In-reply-to: Your message of "Wed, 28 Jun 2000 11:17:24 BST." References: Date: Wed, 28 Jun 2000 10:34:46 -0600 From: Warner Losh Sender: owner-freebsd-new-bus@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Nick Hibma writes: : > I guess I want a "debugging expert" flag that says that I'll fix : > anything that causes a kernel printf and to please just print and fail : > exit rather than do a full panic for silly things. : : There is a number of places where you can't do this in any case. You : can't solve all those fat-finger panics. Yes, but you can solve a whole lot of them. The resource already in use one is the one that kept biting me. For that, you just return a failure. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-new-bus" in the body of the message