Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Cc: Pedro Alves <pedro_alves@portugalmail.pt>, insight@sourceware.org
Subject: Re: syms_from_objfile() warnings and win32-nat.c IO redirection 	(Was: suppress annoying warnings about cygwin1.dbg)
Date: Thu, 28 Jun 2007 12:44:00 -0000	[thread overview]
Message-ID: <20070628104601.GA10328@caradoc.them.org> (raw)
In-Reply-To: <46833EB0.E8ABC8CB@dessent.net>

On Wed, Jun 27, 2007 at 09:53:04PM -0700, Brian Dessent wrote:
> So I tried simply removing the two problematic warnings in
> syms_from_objfile(), and then getting rid of the hacky
> safe_symbol_file_add() wrapper in win32-nat.c.  This obviously has the
> desired effect of not seeing the popups in insight, but now gdb has
> become much more chatty.  This is what happens when you run a Hello
> World program:

Yes, sorry.  You'll want to hold on to that patch a little while, if
you can.  My Windows shared library patches fix both sets of extra
messages.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-06-28 10:46 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] suppress annoying warnings about cygwin1.dbg 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
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 [this message]
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=20070628104601.GA10328@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