linux-kernel - Re: [PATCH 2/3] kgdb, mips: add arch support for the kernel's kgdb core

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20080729.102403.150676958.nemoto@toshiba-tops.co.jp>
Date:	Tue, 29 Jul 2008 10:24:03 +0900 (JST)
From:	Atsushi Nemoto <anemo@....ocn.ne.jp>
To:	jason.wessel@...driver.com
Cc:	linux-kernel@...r.kernel.org, ralf@...ux-mips.org,
	linux-mips@...ux-mips.org
Subject: Re: [PATCH 2/3] kgdb, mips: add arch support for the kernel's kgdb
 core

On Mon, 28 Jul 2008 13:50:55 -0500, Jason Wessel <jason.wessel@...driver.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/