From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3541 invoked by alias); 1 Aug 2008 14:57:43 -0000 Received: (qmail 3527 invoked by uid 22791); 1 Aug 2008 14:57:41 -0000 X-Spam-Check-By: sourceware.org Received: from aussmtpmrkps320.us.dell.com (HELO aussmtpmrkps320.us.dell.com) (143.166.224.254) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 01 Aug 2008 14:57:21 +0000 X-IronPort-AV: E=Sophos;i="4.31,293,1215406800"; d="scan'208";a="368767642" Received: from unknown (HELO M31.equallogic.com) ([12.110.134.31]) by aussmtpmrkps320.us.dell.com with SMTP; 01 Aug 2008 09:57:19 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18579.9292.713618.759108@gargle.gargle.HOWL> Date: Fri, 01 Aug 2008 14:57:00 -0000 From: Paul Koning To: drow@false.org Cc: eliz@gnu.org, apoenitz@trolltech.com, gdb@sources.redhat.com Subject: Re: GDB to C++ issue: deletion References: <200807312204.m6VM4JQM007611@tully.CS.Berkeley.EDU> <200808011054.24219.apoenitz@trolltech.com> <20080801125656.GA14307@caradoc.them.org> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid 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-08/txt/msg00012.txt.bz2 >>>>> "Daniel" == Daniel Jacobowitz writes: Daniel> Sorry, I replied to the wrong list. On Fri, Aug 01, 2008 at Daniel> 12:53:24PM +0300, Eli Zaretskii wrote: >> Still, I think that it is a misrepresentation to say that GDB code >> cannot be understood by "mere mortals". Most problems, as far as >> I remember from questions posted here, are about the high-level >> architectural aspects, asked by those who want to add support for >> some novel or unusual platform. People who need to fix a bug in >> existing code normally don't have much trouble understanding it. Daniel> For what it's worth, that's not my experience at all. Daniel> Contributors have a lot of trouble with the GDB code. One of Daniel> the biggest problems is cleanups, which is one reason I'm Daniel> listening with interest to this conversation. I'll second that. I've done some small scale tweaking and bugfixing, and I found GDB internals hard to navigate. The internals manual is very little help, unfortunately. paul