From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25953 invoked by alias); 17 Apr 2009 10:19:36 -0000 Received: (qmail 25945 invoked by uid 22791); 17 Apr 2009 10:19:36 -0000 X-SWARE-Spam-Status: No, hits=1.4 required=5.0 tests=AWL,BAYES_00,BOTNET,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout1.012.net.il (HELO mtaout1.012.net.il) (84.95.2.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 17 Apr 2009 10:19:28 +0000 Received: from conversion-daemon.i-mtaout1.012.net.il by i-mtaout1.012.net.il (HyperSendmail v2007.08) id <0KI800I00PCXAN00@i-mtaout1.012.net.il> for gdb-patches@sourceware.org; Fri, 17 Apr 2009 13:19:24 +0300 (IDT) Received: from HOME-C4E4A596F7 ([77.126.183.184]) by i-mtaout1.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KI800EMAQ0B5K70@i-mtaout1.012.net.il>; Fri, 17 Apr 2009 13:19:24 +0300 (IDT) Date: Fri, 17 Apr 2009 10:19:00 -0000 From: Eli Zaretskii Subject: Re: DWARF-related warnings in DJGPP build of GDB In-reply-to: <200904171010.n3HAAZBe028822@brahms.sibelius.xs4all.nl> To: Mark Kettenis Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83ljpzk2fn.fsf@gnu.org> References: <834owqmdli.fsf@gnu.org> <83ocuvk497.fsf@gnu.org> <200904171010.n3HAAZBe028822@brahms.sibelius.xs4all.nl> 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/msg00418.txt.bz2 > Date: Fri, 17 Apr 2009 12:10:35 +0200 (CEST) > From: Mark Kettenis > CC: gdb-patches@sourceware.org > > > During symbol reading, DW_AT_type missing from DW_TAG_subrange_type. > > > > This is when debugging a recent snapshot of GDB with itself. > > Which probably means that it used the .gdbinit that is automatically > generated in the build directory, which has > > set complaints 1 > > in it. This makes GDB very picky about the DWARF it is reading. Right. Thanks for pointing this out. That is probably the reason that the DJGPP build complains as well (which was what started this thread): it was also while debugging GDB with itself.