linux-kernel - Re: [announce] kdump2gdb: analyze kdumps with gdb (well, almost)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061009132855.GA25559@in.ibm.com>
Date:	Mon, 9 Oct 2006 09:28:55 -0400
From:	Vivek Goyal <vgoyal@...ibm.com>
To:	Jean-Marc Saffroy <saffroy@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [announce] kdump2gdb: analyze kdumps with gdb (well, almost)

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/