From owner-freebsd-current@FreeBSD.ORG Tue May 20 08:40:44 2003 Return-Path: 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 1A9EB37B40A; Tue, 20 May 2003 08:40:44 -0700 (PDT) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6218A43F85; Tue, 20 May 2003 08:40:43 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-38ldvdp.dialup.mindspring.com ([209.86.253.185] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19I9EC-0000UR-00; Tue, 20 May 2003 08:40:37 -0700 Message-ID: <3ECA4C2A.ECB6E1D2@mindspring.com> Date: Tue, 20 May 2003 08:39:22 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Daniel C. Sobral" References: <3ECA1488.2000602@tcoip.com.br> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4fc3b49889b5ea38eae5e704196b3ed0f350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c cc: Robert Watson cc: CURRENT cc: Julian Elischer Subject: Re: KSE panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Tue, 20 May 2003 15:40:44 -0000 "Daniel C. Sobral" wrote: > This time I don't have a full backtrace because I had just compiled a > new kernel. Anyone knows how do I get kernel.debug installed right along > all the rest of the stuff? :-( Use "config -g GENERIC"; the "-g" option causes the kernel.debug to be created. You don't install "kernel.debug" itself; instead, you install the debug-stripped version, "kernel". When you do a remote debug, or are examining a crash-dump, then you *use* the "kernel.debug" to obtain symbol and debug information. In other words, it's a thing you use post-mortem on a dead kernel, either against a live system sitting in a panic, or against the crashdump image. It's easiest if you build on one machine, and use the other as a sacrificial lamb, so you have all your sources and everything on hand on a non-dead machine to debug the dead one. See also "The FreeBSD Handbook" in the documentation section of the web site, and "info gdb" -- specifically "target remote" and "attach". If you need more help after you get that far, you'll be in a position to post better information for whoever is willing to help you track down the bug. -- Terry