| To: | jason.wessel@windriver.com |
|---|---|
| Subject: | Re: [PATCH 2/3] kgdb, mips: add arch support for the kernel's kgdb core |
| From: | Atsushi Nemoto <anemo@mba.ocn.ne.jp> |
| Date: | Tue, 29 Jul 2008 10:24:03 +0900 (JST) |
| Cc: | linux-kernel@vger.kernel.org, ralf@linux-mips.org, linux-mips@linux-mips.org |
| In-reply-to: | <488E150F.9050508@windriver.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <20080725.235233.130241768.anemo@mba.ocn.ne.jp> <20080728.230512.132304415.anemo@mba.ocn.ne.jp> <488E150F.9050508@windriver.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Committed_AS showing erroneous value, Anirban Sinha |
|---|---|
| Next by Date: | Re: [PATCH v2 1/1][MIPS] Initialization of Alchemy boards, Kevin Hickey |
| Previous by Thread: | Re: [PATCH 2/3] kgdb, mips: add arch support for the kernel's kgdb core, Jason Wessel |
| Next by Thread: | [PATCH] sparse: Make pre_buffer dynamically increasable, Atsushi Nemoto |
| Indexes: | [Date] [Thread] [Top] [All Lists] |