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

[Hui Zhu]

On Thu, Feb 25, 2010 at 05:15, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:
> On Mon, 22 Feb 2010 22:40:16 +0800 Hui Zhu <teawater@xxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/