From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9939 invoked by alias); 18 Oct 2004 20:14:06 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 9932 invoked from network); 18 Oct 2004 20:14:04 -0000 Received: from unknown (HELO blount.mail.mindspring.net) (207.69.200.226) by sourceware.org with SMTP; 18 Oct 2004 20:14:04 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by blount.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1CJdsr-0007ek-00; Mon, 18 Oct 2004 16:13:33 -0400 Received: from mindspring.com (localhost [127.0.0.1]) by berman.michael-chastain.com (Postfix) with SMTP id 4EF0D4B102; Mon, 18 Oct 2004 16:13:48 -0400 (EDT) Date: Mon, 18 Oct 2004 20:14:00 -0000 From: Michael Chastain To: dan@debian.org, eliz@gnu.org Subject: Re: [rfc/NEWS] GDB works with GCC -feliminate-dwarf2-dups. Cc: gdb-patches@sources.redhat.com Message-ID: <417423FA.nailP2L12S6AW@mindspring.com> References: <4172B5F4.nailMEV1154GO@mindspring.com> <20041017183143.GA22628@nevyn.them.org> <4172BF74.nailMK41WRWF5@mindspring.com> <20041017191337.GA23601@nevyn.them.org> <4172D1FF.nailMO5211TI7@mindspring.com> <01c4b4cf$Blat.v2.2.2$1a0e6f00@zahav.net.il> In-Reply-To: <01c4b4cf$Blat.v2.2.2$1a0e6f00@zahav.net.il> User-Agent: nail 10.8 6/28/04 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2004-10/txt/msg00310.txt.bz2 "Eli Zaretskii" wrote: > I don't understand what you are saying ... It's like this. When gdb and gcc don't work together, I have to decide whether I think it's a bug in gdb (so I file a gdb PR) or a bug in gcc (so I file a gcc PR). Some contemplation of this relationship leads me to say: gdb and gcc are truly separate entities. It's not that "gdb X works with gcc Y", it's more exactly "gdb X and gcc Y both support standards Z1, Z2, and Z3". This is especially true because gdb works with other compilers besides gcc, and as far as I know, gcc works with other debuggers besides gdb. It's a subtle point, and even after you see it, you might not agree with it. eli> GDB can now debug programs compiled with the -feliminate-dwarf2-dups eli> option to GCC 3.3.4 or later, as well as programs compiled with eli> proprietary compilers that produce similar debug information (a more eli> compact representation of DWARF-2 debug information using the eli> DW_FORM_ref_addr references). Well, after fooling with this a little bit, I like my version better. I'm comfortable claiming that GDB supports DW_FORM_ref_addr, so that if a compiler produces this information, GDB can support it. I'm not comfortable claiming that GDB can support "programs compiled with proprietary compilers that produce similar debug information". But you're the doco guy, so if you like it that way, go for it. Michael