From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29467 invoked by alias); 15 Apr 2009 20:48:40 -0000 Received: (qmail 29457 invoked by uid 22791); 15 Apr 2009 20:48:39 -0000 X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout2.012.net.il (HELO mtaout2.012.net.il) (84.95.2.4) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 15 Apr 2009 20:48:34 +0000 Received: from conversion-daemon.i_mtaout2.012.net.il by i_mtaout2.012.net.il (HyperSendmail v2004.12) id <0KI500600TP0LR00@i_mtaout2.012.net.il> for gdb-patches@sourceware.org; Wed, 15 Apr 2009 23:48:31 +0300 (IDT) Received: from HOME-C4E4A596F7 ([84.229.34.97]) by i_mtaout2.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KI500JV5TSUHBC0@i_mtaout2.012.net.il>; Wed, 15 Apr 2009 23:48:31 +0300 (IDT) Date: Wed, 15 Apr 2009 20:48:00 -0000 From: Eli Zaretskii Subject: Re: DWARF-related warnings in DJGPP build of GDB In-reply-to: <200904152031.20517.pedro@codesourcery.com> To: Pedro Alves Cc: gdb-patches@sourceware.org, brobecker@adacore.com Reply-to: Eli Zaretskii Message-id: <83d4bdlk2h.fsf@gnu.org> References: <834owqmdli.fsf@gnu.org> <20090415162242.GC7585@adacore.com> <83k55llnv6.fsf@gnu.org> <200904152031.20517.pedro@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-04/txt/msg00353.txt.bz2 > From: Pedro Alves > Date: Wed, 15 Apr 2009 20:31:19 +0100 > Cc: Joel Brobecker > > On Wednesday 15 April 2009 20:26:37, Eli Zaretskii wrote: > > > It could be the compiler emitting wrong debugging info, or the > > > assembler/linker toolchain that screws up. > > > > I will try to upgrade to newer Binutils and to GCC 3.4.4, and see if > > that helps. > ^^^^^ > > Interesting, is there a reason to stay with the gcc 3 series on DJGPP? I'm very conservative in upgrading my development tools. As long as something works fine for me, I'm reluctant to do significant upgrades, because doing so runs a risk of destabilizing the development environment, and with so little free time, I cannot afford that, unless strictly necessary. > I was using DJGPP gcc 4.2.3 last time I tried DJGPP (it's on the wiki), > and it was a prebuilt binary. A DJGPP port of GCC 4.3.2 is available since Sep 2008, but I dislike GCC 4.x because it whines too much about perfectly valid C code. (It may not be a problem with GDB sources, but I compile other projects besides GDB.) So, if GCC 3.4.4 solves the problems I have, I won't have a significant incentive to go to 4.x. > I don't remember if I saw those dwarf issues. May be worth giving > that a shot too. If 3.x won't help, then I might do just that. Thanks.