From: Andrew Morton <akpm@linux-foundation.org>
To: Hui Zhu <teawater@gmail.com>
Cc: Arjan van de Ven <arjan@linux.intel.com>,
ozan@pardus.org.tr, Matthew Wilcox <willy@linux.intel.com>,
linux-kernel@vger.kernel.org,
gdb-patches ml <gdb-patches@sourceware.org>,
Michal Marek <mmarek@suse.cz>,
Jason Wessel <jason.wessel@windriver.com>
Subject: Re: [PATCH 0/2] markup_oops.pl and GDB: Let GDB can handle kernel oops stack message
Date: Wed, 24 Feb 2010 13:15:45 -0800 [thread overview]
Message-ID: <20100224131545.951db05e.akpm@linux-foundation.org> (raw)
In-Reply-To: <4B829750.90107@gmail.com>
On Mon, 22 Feb 2010 22:40:16 +0800 Hui Zhu <teawater@gmail.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?
next prev parent reply other threads:[~2010-02-24 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 14:40 [PATCH 0/2] markup_oops.pl and GDB: Let GDB can handle kernel oops stack message Hui Zhu
2010-02-24 21:15 ` Andrew Morton [this message]
2010-02-25 6:10 ` Hui Zhu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100224131545.951db05e.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=gdb-patches@sourceware.org \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=ozan@pardus.org.tr \
--cc=teawater@gmail.com \
--cc=willy@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox