From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 403 invoked by alias); 11 Jul 2008 16:26:14 -0000 Received: (qmail 395 invoked by uid 22791); 11 Jul 2008 16:26:14 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 11 Jul 2008 16:25:49 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id DD6B998415; Fri, 11 Jul 2008 16:25:47 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id A6B8598376; Fri, 11 Jul 2008 16:25:47 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1KHLRK-0003Yy-IN; Fri, 11 Jul 2008 12:25:46 -0400 Date: Fri, 11 Jul 2008 16:26:00 -0000 From: Daniel Jacobowitz To: Dave Korn Cc: 'Joel Brobecker' , 'Mark Kettenis' , stanshebs@earthlink.net, gdb@sourceware.org Subject: Re: Move GDB to C++ ? Message-ID: <20080711162546.GA13678@caradoc.them.org> Mail-Followup-To: Dave Korn , 'Joel Brobecker' , 'Mark Kettenis' , stanshebs@earthlink.net, gdb@sourceware.org References: <487658F7.1090508@earthlink.net> <200807101901.m6AJ1UMQ007185@brahms.sibelius.xs4all.nl> <48766A88.1050402@earthlink.net> <200807102153.m6ALrjjm017722@brahms.sibelius.xs4all.nl> <20080711062612.GB6132@adacore.com> <003001c8e370$61fcaa10$2708a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <003001c8e370$61fcaa10$2708a8c0@CAM.ARTIMI.COM> User-Agent: Mutt/1.5.17 (2008-05-11) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-07/txt/msg00129.txt.bz2 On Fri, Jul 11, 2008 at 05:08:39PM +0100, Dave Korn wrote: > I think the real issue is that GDB has to be able to debug itself and GDB > is currently weak in a few important areas of C++ support. I think that > should be resolved before we consider porting the code. I don't think it's a big issue. The biggest problems have been resolved; additional problems are mostly in bits of C++ that we would probably avoid anyway. -- Daniel Jacobowitz CodeSourcery