[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <506C37E1.4000305@web.de>
Date: Wed, 03 Oct 2012 15:04:33 +0200
From: Jan Kiszka <jan.kiszka@....de>
To: Andi Kleen <andi@...stfloor.org>
CC: linux-kernel@...r.kernel.org,
Jason Wessel <jason.wessel@...driver.com>,
kgdb-bugreport@...ts.sourceforge.net, Kay Sievers <kay@...y.org>
Subject: Re: [PATCH 06/13] scripts/gdb: Add lx-dmesg command
On 2012-10-03 14:16, Andi Kleen wrote:
> Jan Kiszka <jan.kiszka@....de> writes:
>
>> From: Jan Kiszka <jan.kiszka@...mens.com>
>>
>> This pokes into the log buffer of the debugged kernel, dumping it to the
>> gdb console. Helping in case the target should or can no longer execute
>> dmesg itself.
>
> Thanks. That's very useful. I recently ran into this problem that
> the new log buffer is a pain to dump from qemu gdb.
>
> fwiw there's already some kdump macros in Documentation/kdump
> Since you obsoleted them you could remove those (and for log buffer
> they do not work anymore)
Oh, indeed - and pretty dusty now. I would suggest to remove it when all
its feature are either broken or replaced by python scripts. Need to
look at the details, but stack backtraces is definitely still on the
todo list here.
>
> I don't like the lx-* prefixes.
In this case I think we could add the feature also under "dmesg". But I
would generally like to avoid potential namespace clashes with gdb or
other helpers, therefore the common prefix. Also, if you type
"lx-<tab>", you now get a list of all Linux-related commands.
Jan
Download attachment "signature.asc" of type "application/pgp-signature" (260 bytes)
Powered by blists - more mailing lists