From owner-freebsd-current@FreeBSD.ORG Fri Sep 1 14:15:26 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 D111D16A4DA for ; Fri, 1 Sep 2006 14:15:26 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A1C143D53 for ; Fri, 1 Sep 2006 14:15:25 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id E399946CF5; Fri, 1 Sep 2006 10:15:24 -0400 (EDT) Date: Fri, 1 Sep 2006 15:15:24 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Jos Backus In-Reply-To: <20060829170124.GA1818@lizzy.catnook.local> Message-ID: <20060901151404.C18193@fledge.watson.org> References: <20060829170124.GA1818@lizzy.catnook.local> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: Retrieving info from panics while in X X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Sep 2006 14:15:26 -0000 On Tue, 29 Aug 2006, Jos Backus wrote: > I was wondering if anybody has any plans to address the issue of retrieving > panic/debugging information about crashes happening while X is running. > > For example, -current has been broken for me for several days now; it will > reliably crash within an hour or so while the main thing I'm doing is > running Opera under KDE. But without X, no crash. How does one obtain panic > information in this situation? The typical approaches are: (1) Set up a serial console and use that for debugger work; alternatively, use a firewire console. (2) Set up the system not to entre the debugger, but just to panic and dump core. I prefer the first of those options, myself, since I find the DDB debugging environment extremely useful, especially since it's quite aware of things like the kernel lock environment, etc. Robert N M Watson Computer Laboratory University of Cambridge