public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org,
	Jason Wessel <jason.wessel@windriver.com>,
	kgdb-bugreport@lists.sourceforge.net, Kay Sievers <kay@vrfy.org>
Subject: Re: [PATCH 06/13] scripts/gdb: Add lx-dmesg command
Date: Wed, 03 Oct 2012 15:04:33 +0200	[thread overview]
Message-ID: <506C37E1.4000305@web.de> (raw)
In-Reply-To: <m2iparwy2g.fsf@firstfloor.org>

[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]

On 2012-10-03 14:16, Andi Kleen wrote:
> Jan Kiszka <jan.kiszka@web.de> writes:
> 
>> From: Jan Kiszka <jan.kiszka@siemens.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



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

  reply	other threads:[~2012-10-03 13:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-03 11:21 [PATCH 00/13] Add gdb python scripts as kernel debugging helpers Jan Kiszka
2012-10-03 11:21 ` [PATCH 01/13] scripts/gdb: Add infrastructure Jan Kiszka
2012-10-03 11:21 ` [PATCH 02/13] scripts/gdb: Add container_of helper and convenience function Jan Kiszka
2012-10-03 11:21 ` [PATCH 03/13] scripts/gdb: Add lx-symbols command Jan Kiszka
2012-10-03 11:21 ` [PATCH 04/13] scripts/gdb: Add get_target_endianness helper Jan Kiszka
2012-10-03 11:21 ` [PATCH 05/13] scripts/gdb: Add read_u16/32/64 helpers Jan Kiszka
2012-10-03 11:21 ` [PATCH 06/13] scripts/gdb: Add lx-dmesg command Jan Kiszka
2012-10-03 12:16   ` Andi Kleen
2012-10-03 13:04     ` Jan Kiszka [this message]
2012-10-03 11:21 ` [PATCH 07/13] scripts/gdb: Add task iteration helper Jan Kiszka
2012-10-03 11:21 ` [PATCH 08/13] scripts/gdb: Add helper and convenience function to look up tasks Jan Kiszka
2012-10-03 11:21 ` [PATCH 09/13] scripts/gdb: Add is_target_arch helper Jan Kiszka
2012-10-03 11:21 ` [PATCH 10/13] scripts/gdb: Add internal helper and convenience function to retrieve thread_info Jan Kiszka
2012-10-03 11:21 ` [PATCH 11/13] scripts/gdb: Add get_gdbserver_type helper Jan Kiszka
2012-10-03 11:21 ` [PATCH 12/13] scripts/gdb: Add internal helper and convenience function for per-cpu lookup Jan Kiszka
2012-10-03 11:21 ` [PATCH 13/13] scripts/gdb: Add lx_current convenience function Jan Kiszka
  -- strict thread matches above, loose matches on Subject: below --
2012-11-05 16:08 [PATCH 00/13] Add gdb python scripts as kernel debugging helpers Jan Kiszka
2012-11-05 16:08 ` [PATCH 06/13] scripts/gdb: Add lx-dmesg command Jan Kiszka

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=506C37E1.4000305@web.de \
    --to=jan.kiszka@web.de \
    --cc=andi@firstfloor.org \
    --cc=jason.wessel@windriver.com \
    --cc=kay@vrfy.org \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /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