Date: Tue, 29 Jul 2008 10:24:03 +0900 (JST)
Message-Id: <20080729.102403.150676958.nemoto@toshiba-tops.co.jp>
To: jason.wessel@windriver.com
Cc: linux-kernel@vger.kernel.org, ralf@linux-mips.org,
       linux-mips@linux-mips.org
Subject: Re: [PATCH 2/3] kgdb, mips: add arch support for the kernel's kgdb
 core
From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
In-Reply-To: <488E150F.9050508@windriver.com>
References: <20080725.235233.130241768.anemo@mba.ocn.ne.jp>
	<20080728.230512.132304415.anemo@mba.ocn.ne.jp>
	<488E150F.9050508@windriver.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 999
Lines: 24

On Mon, 28 Jul 2008 13:50:55 -0500, Jason Wessel <jason.wessel@windriver.com> wrote:
> There is no technical reason that frame pointers are required for KGDB
> in the present mainline sources.  This does allow for further
> traceability but it is certainly not a requirement for the use of kgdb.
> If all you want to do is look at frame 0 and inspect memory or set a
> breakpoint and look at some structures kgdb will certainly serve your
> purpose.

Yes.  On MIPS, I can even show backtrace without FRAME_POINTER (if I
enabled DEBUG_INFO).

> I'll consider this a defect to the kgdb core and update the
> documentation to reflect that it is advised to use frame pointers, but
> not a requirement.

Thanks, your patch is fine for me.

---
Atsushi Nemoto
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/