From: Andi Kleen <ak@colin2.muc.de>
To: Keith Owens <kaos@ocs.com.au>
Cc: Andi Kleen <ak@muc.de>,
linas@austin.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: KDB in the mainstream 2.4.x kernels?
Date: 21 Jul 2003 17:06:43 +0200
Date: Mon, 21 Jul 2003 17:06:43 +0200 [thread overview]
Message-ID: <20030721150643.GA70173@colin2.muc.de> (raw)
In-Reply-To: <1681.1058705718@ocs3.intra.ocs.com.au>
On Sun, Jul 20, 2003 at 10:55:18PM +1000, Keith Owens wrote:
> On Fri, 18 Jul 2003 22:43:57 +0200,
> >I actually started on porting the KDB backtracer recently to get
> >reliable frame pointer based backtraces, but it turns out the code
> >for that is so complicated and ugly that the chances of ever merging
> >it would be very slim.
>
> Mainly because the kernel is full of special cases and i386 provides no
Yes I agree. It is an ugly problem, which usually results in ugly
solutions too.
-Andi
next prev parent reply other threads:[~2003-07-21 14:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aJIn.3mj.15@gated-at.bofh.it>
2003-07-18 20:43 ` KDB in the mainstream 2.4.x kernels? Andi Kleen
2003-07-19 0:31 ` linas
2003-07-19 0:57 ` Andi Kleen
2003-07-20 12:55 ` Keith Owens
2003-07-20 13:31 ` David S. Miller
2003-07-20 22:27 ` Keith Owens
2003-07-21 15:06 ` Andi Kleen [this message]
2003-07-29 19:44 ` Robin Holt
2003-08-13 4:40 ` Martin Pool
2003-08-13 11:04 ` Andi Kleen
2003-08-25 12:16 ` Greg Stark
2003-08-25 16:23 ` Andi Kleen
2003-08-26 13:39 ` Greg Stark
2003-08-27 13:49 ` Alan Cox
2003-08-30 10:35 ` Pavel Machek
2003-09-02 20:40 Tolentino, Matthew E
-- strict thread matches above, loose matches on Subject: below --
2003-08-28 17:08 Tolentino, Matthew E
2003-08-28 20:24 ` Alan Cox
2003-07-18 20:06 linas
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=20030721150643.GA70173@colin2.muc.de \
--to=ak@colin2.muc.de \
--cc=ak@muc.de \
--cc=kaos@ocs.com.au \
--cc=linas@austin.ibm.com \
--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;
as well as URLs for NNTP newsgroup(s).