From owner-freebsd-new-bus Tue Jun 27 12:18:48 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 4DD9437B70B for ; Tue, 27 Jun 2000 12:18:38 -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 NAA75542; Tue, 27 Jun 2000 13:18:36 -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 NAA48317; Tue, 27 Jun 2000 13:16:44 -0600 (MDT) Message-Id: <200006271916.NAA48317@harmony.village.org> To: Nick Hibma Subject: Re: Debugger vs panic Cc: new-bus@FreeBSD.ORG In-reply-to: Your message of "Tue, 27 Jun 2000 11:59:41 BST." References: Date: Tue, 27 Jun 2000 13:16:44 -0600 From: Warner Losh Sender: owner-freebsd-new-bus@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Nick Hibma writes: : He was quite persistent in his opinion that it was a bug in the code and : could only lead to faults later in the code. He'd rather have the : problem pointed out right where it occurs. And I agree with him to the : extent that if there is a problem it should go pop as early as possible : in the appropriate place, and not at a later stage where you will have : to trace back to the place where the value was last written, which might : be complicated to say the least. I'd rather have a #define that I can give to have it fail out rather than panic. Why? I don't like rebuildnig my disks. When I'm debugging new drivers, I tend to make bonehead mistakes, especially in the bridge driver I'm working on. I've wasted lots and lots of time because of these panics. It would be nicer if I could #define way the panic when I want. For most people, they will want to keep the panics. For me, and other ard core developers the panics do negative good. 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. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-new-bus" in the body of the message