From: Andi Kleen <ak@suse.de>
To: jmerkey <jmerkey@utah-nac.org>
Subject: Re: [PATCH 0/39] NLKD - Novell Linux Kernel Debugger
Date: Sun, 13 Nov 2005 04:44:44 +0100
User-Agent: KMail/1.8.2
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>, Jan Beulich <JBeulich@novell.com>,
       linux-kernel@vger.kernel.org, akpm@osdl.org
References: <43720DAE.76F0.0078.0@novell.com> <p73u0eh4als.fsf@verdi.suse.de> <4376AAC1.5060503@utah-nac.org>
In-Reply-To: <4376AAC1.5060503@utah-nac.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200511130444.45468.ak@suse.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 797
Lines: 20

On Sunday 13 November 2005 03:53, jmerkey wrote:

> Yes. This is the way to go. Use kdb as a base and instrument an 
> alternate debugger interface. You need to also find a good way to
> allow GDB to work properly with alternate debuggers. At present, the 
> code in traps.c is mutually exclusive since embedded int3
> breakpoints trigger in the kernel for gbd. This is busted.


I don't think we'll support stacking multiple kernel debuggers (except
for special cases like kprobes+another debugger). It's complicated
and probably not worth it.

-Andi

-
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/