linux-kernel - Re: [PATCH 0/2] markup_oops.pl and GDB: Let GDB can handle kernel oops stack message

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 24 Feb 2010 13:15:45 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Hui Zhu <teawater@...il.com>
Cc:	Arjan van de Ven <arjan@...ux.intel.com>, ozan@...dus.org.tr,
	Matthew Wilcox <willy@...ux.intel.com>,
	linux-kernel@...r.kernel.org,
	gdb-patches ml <gdb-patches@...rceware.org>,
	Michal Marek <mmarek@...e.cz>,
	Jason Wessel <jason.wessel@...driver.com>
Subject: Re: [PATCH 0/2] markup_oops.pl and GDB: Let GDB can handle kernel
 oops stack message

On Mon, 22 Feb 2010 22:40:16 +0800 Hui Zhu <teawater@...il.com> wrote:

> So I make a patch for markup_oops.pl to make it can convert the oops
> message to GDB command.
> And make a patch for GDB to add a new target empty which level is same
> with corelow target. It can save the memory and reg operation command's
> value and send it to GDB as the inferior's value. Then GDB can parse the
> oops message directly.

How useful is the kernel patch when one is using an unpatched gdb?
--
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/