Date: Mon, 17 Jan 2005 10:07:36 +0000 (GMT)
From: Tigran Aivazian <tigran@veritas.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andi Kleen <ak@suse.de>, Adrian Bunk <bunk@stusta.de>, discuss@x86-64.org,
       linux-kernel@vger.kernel.org
Subject: Re: [discuss] Re: [2.6 patch] x8664_ksyms.c: unexport register_die_notifier
In-Reply-To: <1105955659.6304.62.camel@laptopd505.fenrus.org>
Message-ID: <Pine.LNX.4.61.0501171006100.4644@ezer.homenet>
References: <20050116074649.GW4274@stusta.de>  <20050117092654.GB29270@wotan.suse.de>
 <1105955659.6304.62.camel@laptopd505.fenrus.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1138
Lines: 26

On Mon, 17 Jan 2005, Arjan van de Ven wrote:

> On Mon, 2005-01-17 at 10:26 +0100, Andi Kleen wrote:
>> On Sun, Jan 16, 2005 at 08:46:49AM +0100, Adrian Bunk wrote:
>>> The only user of register_die_notifier (kernel/kprobes.c) can't be
>>> built modular. Therefore, it's the EXPORT_SYMBOL is superfluous.
>>
>> Please don't apply this, it was especially intended for modular debuggers.
>> There is already a hacvked kdb around that uses it.
>
> eh didn't Tigran just mail lkml claiming that kdb and x86-64 really
> don't mix ??

No, I emailed saying that kdb on x86_64 does NOT show the values of 
parameters passed to functions in the backtrace. And, ok, it has some 
other bugs (e.g. reboot doesn't work on SMP) too. But generally speaking 
kdb does work on x86_64. It just still has bugs, but so does every piece 
of software. We should just fix them all, that's all :)

Kind regards
Tigran
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/