From: Andi Kleen <ak@suse.de>
To: piet@bluelane.com
Cc: Andrew Morton <akpm@osdl.org>,
kgdb-bugreport@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
George Anzinger <george@wildturkeyranch.net>,
vgoyal@in.ibm.com, Subhachandra Chandra <schandra@bluelane.com>,
"Discussion list for crash utility usage,
maintenance and development" <crash-utility@redhat.com>
Subject: Re: [RFC] [Crash-utility] Patch to use gdb's bt in crash - works great with kgdb! - KGDB in Linus Kernel.
Date: 31 Aug 2006 16:07:15 +0200 [thread overview]
Message-ID: <p73lkp5578s.fsf@verdi.suse.de> (raw)
In-Reply-To: <1156976522.24314.1.camel@piet2.bluelane.com>
Piet Delaney <piet@bluelane.com> writes:
> >
> > ENOPATCH
>
> Opps.
What an ugly patch!
But it should be totally obsolete with the unwinder work Jan and me have been
doing recently which does this all properly. .18 isn't quite there
yet in all cases, but .19 will be hopefully.
-Andi
next prev parent reply other threads:[~2006-08-31 14:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44EC8CA5.789286A@redhat.com>
[not found] ` <20060824111259.GB22145@in.ibm.com>
[not found] ` <44EDA676.37F12263@redhat.com>
[not found] ` <1156966522.29300.67.camel@piet2.bluelane.com>
[not found] ` <20060830204032.GD30392@in.ibm.com>
2006-08-30 21:41 ` [RFC] [Crash-utility] Patch to use gdb's bt in crash - works great with kgdb! - KGDB in Linus Kernel Piet Delaney
2006-08-30 21:48 ` Andrew Morton
2006-08-30 22:57 ` Andrew Morton
2006-08-31 2:42 ` How about an enumerated list of issues with the existing kgdb patches? Piet Delaney
2006-08-31 3:00 ` Andrew Morton
2006-12-13 8:32 ` Piet Delaney
2006-08-30 21:53 ` [RFC] [Crash-utility] Patch to use gdb's bt in crash - works great with kgdb! - KGDB in Linus Kernel Randy.Dunlap
2006-08-30 22:22 ` Piet Delaney
2006-08-31 14:07 ` Andi Kleen [this message]
2006-08-31 14:20 ` [Kgdb-bugreport] " Tom Rini
2006-08-31 14:43 ` Andi Kleen
2006-08-31 20:41 ` Piet Delaney
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=p73lkp5578s.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=crash-utility@redhat.com \
--cc=george@wildturkeyranch.net \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=piet@bluelane.com \
--cc=schandra@bluelane.com \
--cc=vgoyal@in.ibm.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