From owner-freebsd-current@FreeBSD.ORG Fri Apr 9 07:27:26 2004 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 C681816A4CE for ; Fri, 9 Apr 2004 07:27:26 -0700 (PDT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B22543D3F for ; Fri, 9 Apr 2004 07:27:26 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.10/8.12.10) id i39ERPre035103; Fri, 9 Apr 2004 09:27:25 -0500 (CDT) (envelope-from dan) Date: Fri, 9 Apr 2004 09:27:25 -0500 From: Dan Nelson To: Xin LI Message-ID: <20040409142725.GA8811@dan.emsphone.com> References: <20040409061800.GA2000@frontfree.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040409061800.GA2000@frontfree.net> X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: How to produce effective backtraces from crashdump? 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: Fri, 09 Apr 2004 14:27:26 -0000 In the last episode (Apr 09), Xin LI said: > I'm encounting a very strange problem when trying to obtain > backtraces from a recently compiled kernel (see attachments for my > dmesg.boot, kernel configuration, and /etc/make.conf). > > To make the long story short, here's my rough situation: I have built > a customized kernel with makeoptions DEBUG=-g, and no special options > in /etc/make.conf. When system is restarted after a panic, and when I > open it with: > > gdb -k /usr/obj/usr/src/sys/BEASTIE/kernel.debug /var/crash/vmcore.0 > > then have a "bt full" I got something like this: > > (kgdb) bt full > #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:236 > No locals. > #1 0xc04f63ae in ?? () > No symbol table info available. I can't help you with your symbol problem, but if you add the DDB_TRACE option to your kernel config, the kernel will print a simple backtrace (function names and arguments) on panic, which is sometimes enough info to track down the problem. -- Dan Nelson dnelson@allantgroup.com