Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761452AbYHEPkz (ORCPT ); Tue, 5 Aug 2008 11:40:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758771AbYHEPkL (ORCPT ); Tue, 5 Aug 2008 11:40:11 -0400 Received: from 166-70-238-42.ip.xmission.com ([166.70.238.42]:34508 "EHLO ns1.wolfmountaingroup.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758726AbYHEPkK (ORCPT ); Tue, 5 Aug 2008 11:40:10 -0400 Message-ID: <44919.166.70.238.45.1217949560.squirrel@webmail.wolfmountaingroup.com> In-Reply-To: <200808060133.10457.nickpiggin@yahoo.com.au> References: <17494.166.70.238.46.1217784156.squirrel@webmail.wolfmountaingroup.com> <33030.166.70.238.45.1217948565.squirrel@webmail.wolfmountaingroup.com> <200808060133.10457.nickpiggin@yahoo.com.au> Date: Tue, 5 Aug 2008 09:19:20 -0600 (MDT) Subject: Re: [ANNOUNCE] Merkey's Kernel Debugger From: jmerkey@wolfmountaingroup.com To: "Nick Piggin" Cc: jmerkey@wolfmountaingroup.com, "Geert Uytterhoeven" , "Stefan Richter" , "Josh Boyer" , linux-kernel@vger.kernel.org User-Agent: SquirrelMail/1.4.6 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Priority: 3 (Normal) Importance: Normal Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1662 Lines: 43 > On Wednesday 06 August 2008 01:02, jmerkey@wolfmountaingroup.com wrote: >> > On Mon, 4 Aug 2008, jmerkey@wolfmountaingroup.com wrote: > >> > -- >> > Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- >> > geert@linux-m68k.org >> >> No I was not, but I am now. At any rate, I removed the Microsoft-isms >> from the code. I can cut yet another patch for git6, but git5 was there >> -- GPL2 and all. How about putting in into the kernel guys -- :-) > > Seriously? Because it doesn't seem to have had enough peer review, > it hasn't had widespread testing in somewhere like linux-next or > -mm, and we already have kgdb so you have to also explain why you > can't improve kgdb in the areas it trails mdb. If you go back to LKML from 2000, this debugger has been around for 10 years. I agree not in the hands of the public, but its very mature in comparison to kdb or kgdb. > > But the ideal outcome would be if you could contribute patches to > kgdb to the point where it is as good as mdb. It is already in the > tree and supported by a handful of architectures... any chance of > that? (I don't know kernel debugger code, so I ask as an interested > user) > I plan to work on kdb and yes, there is a version of this that runs as an alternate debugger of kdb - you can even switch back and forth between them - but that misses the point as well. I can wait untl its more widespread -- or not. Jeff -- 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/