From: Andi Kleen <andi@firstfloor.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Jason Wessel <jason.wessel@windriver.com>,
kgdb-bugreport@lists.sourceforge.net,
Andi Kleen <andi@firstfloor.org>, Tom Tromey <tromey@redhat.com>,
Ben Widawsky <ben@bwidawsk.net>
Subject: Re: [PATCH v4 03/13] scripts/gdb: Add lx-symbols command
Date: Mon, 21 Jan 2013 22:19:20 +0100 [thread overview]
Message-ID: <20130121211920.GP30577@one.firstfloor.org> (raw)
In-Reply-To: <2ce8613114b7af6da0b55bdab8c38c69024fbd13.1358787929.git.jan.kiszka@siemens.com>
On Mon, Jan 21, 2013 at 06:06:10PM +0100, Jan Kiszka wrote:
> This is probably the most useful helper when debugging kernel modules:
> lx-symbols will first reload vmlinux. Then it searches recursively for
> *.ko files in the specified paths and the current directory. Finally it
> walks the kernel's module list, issuing the necessary add-symbol-file
> command for each loaded module so that gdb know which module symbol
> correspond to which address.
Yes sounds very useful. I usually have to build everything
statically for gdb debugging. Would definitely use it if it was
in the standard tree.
-Andi
next prev parent reply other threads:[~2013-01-21 21:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 17:06 [PATCH v4 00/13] Add gdb python scripts as kernel debugging helpers Jan Kiszka
2013-01-21 17:06 ` [PATCH v4 01/13] scripts/gdb: Add infrastructure Jan Kiszka
2013-01-23 11:41 ` Borislav Petkov
2013-01-23 11:44 ` Jan Kiszka
2013-01-23 12:01 ` Borislav Petkov
2013-01-23 12:04 ` Jan Kiszka
2013-01-21 17:06 ` [PATCH v4 02/13] scripts/gdb: Add container_of helper and convenience function Jan Kiszka
2013-01-21 17:06 ` [PATCH v4 03/13] scripts/gdb: Add lx-symbols command Jan Kiszka
2013-01-21 21:19 ` Andi Kleen [this message]
2013-01-21 17:06 ` [PATCH v4 04/13] scripts/gdb: Add get_target_endianness helper Jan Kiszka
2013-01-21 17:06 ` [PATCH v4 05/13] scripts/gdb: Add read_u16/32/64 helpers Jan Kiszka
2013-01-21 17:06 ` [PATCH v4 06/13] scripts/gdb: Add lx-dmesg command Jan Kiszka
2013-01-21 21:20 ` Andi Kleen
2013-01-21 17:06 ` [PATCH v4 07/13] scripts/gdb: Add task iteration helper Jan Kiszka
2013-01-21 17:06 ` [PATCH v4 08/13] scripts/gdb: Add helper and convenience function to look up tasks Jan Kiszka
2013-01-21 17:06 ` [PATCH v4 09/13] scripts/gdb: Add is_target_arch helper Jan Kiszka
2013-01-21 17:06 ` [PATCH v4 10/13] scripts/gdb: Add internal helper and convenience function to retrieve thread_info Jan Kiszka
2013-01-21 17:06 ` [PATCH v4 11/13] scripts/gdb: Add get_gdbserver_type helper Jan Kiszka
2013-01-21 17:06 ` [PATCH v4 12/13] scripts/gdb: Add internal helper and convenience function for per-cpu lookup Jan Kiszka
2013-01-21 17:06 ` [PATCH v4 13/13] scripts/gdb: Add lx_current convenience function Jan Kiszka
2013-01-21 21:21 ` [PATCH v4 00/13] Add gdb python scripts as kernel debugging helpers Andi Kleen
2013-01-22 8:36 ` Jan Kiszka
2013-01-21 22:06 ` Ben Widawsky
2013-01-21 22:15 ` Andi Kleen
2013-01-22 8:44 ` Jan Kiszka
2013-01-23 11:32 ` Borislav Petkov
2013-01-23 11:40 ` Jan Kiszka
2013-01-24 20:18 ` [PATCH v4 14/13] scripts/gdb: Add basic documentation 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=20130121211920.GP30577@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=ben@bwidawsk.net \
--cc=jan.kiszka@siemens.com \
--cc=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tromey@redhat.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