From owner-freebsd-stable@FreeBSD.ORG Thu Jun 2 16:16:18 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 83F9E16A41C for ; Thu, 2 Jun 2005 16:16:18 +0000 (GMT) (envelope-from takeda@takeda.tk) Received: from chinatsu.takeda.tk (node-402413e2.sna.onnet.us.uu.net [64.36.19.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 436AB43D1D for ; Thu, 2 Jun 2005 16:16:13 +0000 (GMT) (envelope-from takeda@takeda.tk) Received: from takeda.lan (takeda.lan [10.0.0.3]) (authenticated bits=0) by chinatsu.takeda.tk (8.13.3/8.13.1) with ESMTP id j52GGCpL015823 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Thu, 2 Jun 2005 09:16:12 -0700 (PDT) (envelope-from takeda@takeda.tk) Date: Thu, 2 Jun 2005 09:11:23 -0700 From: =?Windows-1250?Q?Derek_Kuli=F1ski?= X-Priority: 3 (Normal) Message-ID: <5010392255.20050602091123@takeda.tk> To: Kris Kennaway In-Reply-To: <20050602073739.GB2756@xor.obsecurity.org> References: <8910581751.20050529112956@takeda.tk> <20050602073739.GB2756@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=Windows-1250 Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV 0.85.1/907/Thu Jun 2 05:50:12 2005 on chinatsu.takeda.tk X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org Subject: Re: stack backtrace 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: Thu, 02 Jun 2005 16:16:18 -0000 Hello Kris, Thursday, June 2, 2005, 12:37:41 AM, you wrote: > It looks like debugging code (it's been removed in -current). > Jeff: > in 1.141 of ffs_softdep.c you added a call to backtrace() if bp->b_vp > == NULL..you removed it in current in 1.166, but some people are > seeing it trigger on 5.x So it's harmless? As for debugging, I compiled kernel with: makeoptions DEBUG=-g options KDB options KDB_TRACE options DDB To have coredump, if system crashes (I didn't oticed any slowdown, so I guess it doesn't hurt) Are those last three options necessary to get core? Or is only DEBUG=-g needed? -- Best regards, Derek mailto:takeda@takeda.tk CCNA, SCSA, SCNA, LPIC, MCP certified http://www.takeda.tk Trying to outsmart a compiler defeats much of the purpose of using one. -- Kernighan & Plauger, "The Elements of Programming Style"