From owner-freebsd-current@FreeBSD.ORG Wed Apr 6 12:45:14 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0AB471065670; Wed, 6 Apr 2011 12:45:14 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id D7C4C8FC13; Wed, 6 Apr 2011 12:45:13 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 897FE46B49; Wed, 6 Apr 2011 08:45:13 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 2174B8A02B; Wed, 6 Apr 2011 08:45:13 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 6 Apr 2011 08:37:50 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110325; KDE/4.5.5; amd64; ; ) References: <4D9A4CE5.5090900@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201104060837.50411.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Wed, 06 Apr 2011 08:45:13 -0400 (EDT) Cc: Justin Hibbits , FreeBSD Current Subject: Re: KGDB stack traces in the kernel. 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: Wed, 06 Apr 2011 12:45:14 -0000 On Monday, April 04, 2011 9:04:23 pm Justin Hibbits wrote: > On Apr 4, 2011, at 6:57 PM, Julian Elischer wrote: > > is there anyone here with enough gdb/kgdb source experience to know > > what > > we would need to put on the stack at fork_exit() to make it stop > > when it > > gets there? > > > > not only is it annoying but it slows down debugging because kgdb and > > the ddd > > front end ask for stacks a LOT. sometimes it actually just hangs as > > the stack > > goes into a loop and never ends. > > > > I had a quick look but didn't spot how gdb decides it has reached > > the end of a stack. > > > > Julian > > From my experience, it checks for a NULL stack chain pointer. Once > that reaches NULL, it's the end of the stack. No, I removed that because it broke debugging panics due to NULL function pointers. -- John Baldwin