From owner-cvs-src@FreeBSD.ORG Tue Jan 20 18:51:24 2004 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D9E5E16A4CE; Tue, 20 Jan 2004 18:51:24 -0800 (PST) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADB1E43D39; Tue, 20 Jan 2004 18:51:23 -0800 (PST) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id i0L2pB7E060404; Tue, 20 Jan 2004 18:51:15 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <200401210251.i0L2pB7E060404@gw.catspoiler.org> Date: Tue, 20 Jan 2004 18:51:11 -0800 (PST) From: Don Lewis To: nate@root.org In-Reply-To: <20040120164435.I98793@root.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: grog@FreeBSD.org cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: phk@FreeBSD.org cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/alpha/alpha support.s src/sys/i386/i386 swtch.s src/sys/kern kern_shutdown.c src/sys/sys systm.h X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2004 02:51:25 -0000 On 20 Jan, Nate Lawson wrote: > On Wed, 21 Jan 2004, Greg 'groggy' Lehey wrote: >> On Tuesday, 20 January 2004 at 11:31:03 -0800, Nate Lawson wrote: >> > * GDB over Ethernet >> >> We have GDB over firewire. Ethernet would be nice too, but firewire >> actually does more. Take a look at gdb(4) (new man page). > > I'm glad to have this. More machines have ethernet than firewire ports > though. > >> > We don't need file/line added to the panic message since panic >> > messages are unambiguous. >> >> You still need to grep for them. > > There are basically two kinds of panics: assertions and page faults. > Assertions, whether KASSERT or explicit checks/panic calls, give a unique, > easily identified message ("foo driver: invalid mbuf length, %d"). If > this is not obvious enough even without grep, then the panic message > should be fixed. There is no difference between "vi +line file.c" and > "vi file.c /msg", hence phk's commit is not useful in this case. > > Page faults are much harder to track down from the start. You find > whether or not it was a NULL pointer, the curproc, and PC. So the next > step is to have them recompile with options DDB or preferably -g and type > "tr" at the DDB prompt. The changes to panic do not help this case at all > since you get the file and line of the page fault handler. I'll put in a request for page faults to report the file and line number where the trap occurred ;-)