From: Daniel Jacobowitz <drow@false.org>
To: Pedro Alves <pedro_alves@portugalmail.pt>
Cc: insight@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [patch ping^2] suppress annoying warnings about cygwin1.dbg
Date: Mon, 25 Jun 2007 23:52:00 -0000 [thread overview]
Message-ID: <20070625234015.GA17640@caradoc.them.org> (raw)
In-Reply-To: <46804DAD.4020309@portugalmail.pt>
On Tue, Jun 26, 2007 at 12:20:13AM +0100, Pedro Alves wrote:
> I think the changes to make win32 use solib-target.c at least will
> turn this into a different warning, if they don't remove it. I'm
> not familiar with the separate debug info mechanism in gdb, but to
> me it sounds we should understand the reasons for the warnings and
> fix it there. I mean, why is it that these warnings don't happen
> on other targets? Why is gdb looking for loadable sections in a
> debug info only file?
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.
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
posted WIP patch removed it. I think it did for most but not all
cases.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-06-25 23:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46262D3A.8B1A0D15@dessent.net>
[not found] ` <20070418150137.GA7338@trixie.casa.cgf.cx>
[not found] ` <46263710.D9755DAD@dessent.net>
[not found] ` <462639F3.FBCF4675@dessent.net>
[not found] ` <46264A56.BA86EED7@dessent.net>
2007-05-02 15:19 ` [patch ping] " Brian Dessent
2007-06-25 23:20 ` [patch ping^2] " Brian Dessent
2007-06-25 23:40 ` Pedro Alves
2007-06-25 23:52 ` Daniel Jacobowitz [this message]
2007-06-26 0:59 ` Brian Dessent
2007-06-26 7:37 ` Daniel Jacobowitz
2007-06-28 6:11 ` syms_from_objfile() warnings and win32-nat.c IO redirection (Was: suppress annoying warnings about cygwin1.dbg) Brian Dessent
2007-06-28 12:44 ` Daniel Jacobowitz
2007-10-11 20:26 ` Daniel Jacobowitz
2007-10-13 0:09 ` Brian Dessent
2007-10-13 1:44 ` Pedro Alves
2007-10-13 2:49 ` Brian Dessent
2007-10-13 3:33 ` Pedro Alves
2007-10-13 6:03 ` Brian Dessent
2007-10-24 19:06 ` Daniel Jacobowitz
2007-10-29 3:06 ` Pedro Alves
2007-10-29 12:33 ` Pedro Alves
2007-10-29 12:57 ` Daniel Jacobowitz
2007-10-29 22:54 ` Pedro Alves
2007-10-30 4:05 ` Christopher Faylor
2007-10-30 9:02 ` Pedro Alves
2007-10-30 1:27 ` Christopher Faylor
2007-11-08 23:56 ` Pedro Alves
2007-11-09 1:35 ` Pedro Alves
2007-11-09 13:34 ` Christopher Faylor
2007-11-09 13:59 ` Daniel Jacobowitz
2007-11-09 13:59 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070625234015.GA17640@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=insight@sourceware.org \
--cc=pedro_alves@portugalmail.pt \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox