From: Vivek Goyal <vgoyal@in.ibm.com>
To: Jean-Marc Saffroy <saffroy@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [announce] kdump2gdb: analyze kdumps with gdb (well, almost)
Date: Mon, 9 Oct 2006 09:28:55 -0400 [thread overview]
Message-ID: <20061009132855.GA25559@in.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0610061742270.9250@erda.mds>
On Fri, Oct 06, 2006 at 06:42:00PM +0200, Jean-Marc Saffroy wrote:
> Hello folks,
>
> Following earlier discussions on how nice it would be to use gdb on kdump
> cores, I took some time and wrote a small tool to do just that:
> http://jeanmarc.saffroy.free.fr/kdump2gdb/
>
> The main limitation is that there is absolutely no backtrace of
> non-running tasks yet, but I will try to see how it can be done. Also, it
> works only on x86-64, but people are welcome to contribute ports. :)
Hi Jean,
Interesting stuff. Documentation/kdump/gdbmacros.txt already seems to
be containing various macros for seeing the back traces of non-running
threads. Won't these help?
-Vivek
next prev parent reply other threads:[~2006-10-09 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 16:42 [announce] kdump2gdb: analyze kdumps with gdb (well, almost) Jean-Marc Saffroy
2006-10-09 13:28 ` Vivek Goyal [this message]
2006-10-10 18:57 ` Jean-Marc Saffroy
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=20061009132855.GA25559@in.ibm.com \
--to=vgoyal@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=saffroy@gmail.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