From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13678 invoked by alias); 26 Jun 2007 00:53:31 -0000 Received: (qmail 13663 invoked by uid 22791); 26 Jun 2007 00:53:30 -0000 X-Spam-Check-By: sourceware.org Received: from dessent.net (HELO dessent.net) (69.60.119.225) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 26 Jun 2007 00:53:26 +0000 Received: from localhost ([127.0.0.1] helo=dessent.net) by dessent.net with esmtp (Exim 4.50) id 1I2zJ2-0001PJ-3S; Tue, 26 Jun 2007 00:53:20 +0000 Message-ID: <4680637F.A8C3E408@dessent.net> Date: Tue, 26 Jun 2007 00:59:00 -0000 From: Brian Dessent Reply-To: gdb-patches@sourceware.org X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: Daniel Jacobowitz CC: Pedro Alves , insight@sourceware.org, gdb-patches@sourceware.org Subject: Re: [patch ping^2] suppress annoying warnings about cygwin1.dbg References: <46262D3A.8B1A0D15@dessent.net> <20070418150137.GA7338@trixie.casa.cgf.cx> <46263710.D9755DAD@dessent.net> <462639F3.FBCF4675@dessent.net> <46264A56.BA86EED7@dessent.net> <4638AB6B.5AA94B26@dessent.net> <46803846.F99470AE@dessent.net> <46804DAD.4020309@portugalmail.pt> <20070625234015.GA17640@caradoc.them.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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: 2007-06/txt/msg00454.txt.bz2 Daniel Jacobowitz wrote: > There are loadable sections in an ELF debug-only file; they all have > type NOBITS instead of PROGBITS, but are otherwise unchanged. I'm > going to make a wild guess here that says you can't do that in > PE-COFF, so the text section is actually missing. So probably we > should figure out whether we're loading a debug-info-only file at this > point, and not issue those warnings. Or else remove the warnings > entirely. Ah, wish I'd known that at the time: So, the proper way then would be to set some flag if we're reading a .gnu-debuglink file and not generate the warnings in the first place? I can try to come up with something along those lines then. > The redirection to /dev/null is silly and should go away, by the way, > so relying on it isn't the right fix. I don't remember if my recently Right, it always looked pretty ugly to me, but when I initially started looking at this I just wanted insight to shut the **** up. Brian