Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
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: Thu, 25 Feb 2010 06:10:00 -0000	[thread overview]
Message-ID: <daef60381002242210x39063662xfb0152d2c395ed70@mail.gmail.com> (raw)
In-Reply-To: <20100224131545.951db05e.akpm@linux-foundation.org>

On Thu, Feb 25, 2010 at 05:15, Andrew Morton <akpm@linux-foundation.org> wrote:
> 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?
>

For that status, I have 2 ways to handle it:
1.  Change the "target empty" to other target, like "target remote
localhost:1234".
Then the remote target displace the empty target.  It can be use.

2.  In http://lkml.org/lkml/2010/1/3/28, there is a program called
s2c, it can convert some special message to a core file.  Then gdb can
parse core file.
If you think we need it, I can make it input the gdb commands.

Thanks,
Hui


      reply	other threads:[~2010-02-25  6:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-22 14:40 Hui Zhu
2010-02-24 21:16 ` Andrew Morton
2010-02-25  6:10   ` Hui Zhu [this message]

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=daef60381002242210x39063662xfb0152d2c395ed70@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=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=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