From owner-freebsd-current@FreeBSD.ORG Fri Sep 1 13:58:00 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 BD5F916A4FB for ; Fri, 1 Sep 2006 13:57:55 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 713BA43D67 for ; Fri, 1 Sep 2006 13:57:55 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id k81Dvmjq035218; Fri, 1 Sep 2006 09:57:48 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org, jos@catnook.com Date: Fri, 1 Sep 2006 09:57:29 -0400 User-Agent: KMail/1.9.1 References: <20060829170124.GA1818@lizzy.catnook.local> In-Reply-To: <20060829170124.GA1818@lizzy.catnook.local> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200609010957.30289.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [192.168.0.1]); Fri, 01 Sep 2006 09:57:49 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/1784/Fri Sep 1 08:00:05 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: 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 13:58:00 -0000 On Tuesday 29 August 2006 13:01, 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? set debug.debugger_on_panic to 0 as a workaround for now. -- John Baldwin