From owner-freebsd-stable@FreeBSD.ORG Sat Jul 30 19:52:29 2011 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 57F4C106566B for ; Sat, 30 Jul 2011 19:52:29 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id A1CD28FC12 for ; Sat, 30 Jul 2011 19:52:28 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id WAA29779; Sat, 30 Jul 2011 22:52:26 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QnFaE-0008M9-4n; Sat, 30 Jul 2011 22:52:26 +0300 Message-ID: <4E3460F9.7090909@FreeBSD.org> Date: Sat, 30 Jul 2011 22:52:25 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110706 Thunderbird/5.0 MIME-Version: 1.0 To: maestro something References: <4E2E9F60.1060808@FreeBSD.org> <4E33B7CF.90200@FreeBSD.org> <4E344D15.1040508@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.2pre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org Subject: Re: dtrace ustack kernel panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Jul 2011 19:52:29 -0000 on 30/07/2011 22:05 maestro something said the following: > fb82i386# cat /etc/make.conf > CFLAGS= -O > > (accodring to man make.conf only -O and -O2 is supported for CFLAGS anyways) > > kernel.debug is the newly compiled kernel (according to the timestamp) > > fb82i386# kgdb kernel.debug /var/crash/vmcore.0 Is vmcore.0 also new (i.e. produced with the new kernel)? Does 'list ...' command still produces no useful output? P.S. Also, hmm, I think that you shouldn't run kgdb on kernel.debug, just to avoid any confusion... I think that you should run something like kgdb /boot/${your installed kernel}/kernel /var/crash/vmcore.0; the debug symbols are automatically picked up from *.symbols files in the kernel directory. -- Andriy Gapon