Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Brian Dessent <brian@dessent.net>
To: insight@sourceware.org
Cc: gdb-patches@sourceware.org
Subject: Re: [patch ping^2] suppress annoying warnings about cygwin1.dbg
Date: Mon, 25 Jun 2007 23:20:00 -0000	[thread overview]
Message-ID: <46803846.F99470AE@dessent.net> (raw)
In-Reply-To: <4638AB6B.5AA94B26@dessent.net>

Brian Dessent wrote:

> > gdb/
> > 2007-04-18  Brian Dessent  <brian@dessent.net>
> >
> >         * ui-file.c (ui_file_isnull): New function.
> >         * ui-file.h (ui_file_isnull): Add declaration.
> >
> > gdb/gdbtk/
> > 2007-04-18  Brian Dessent  <brian@dessent.net>
> >
> >         * generic/gdbtk-hooks.c (gdbtk_warning): Do not process the warning
> >         if gdb_stdout has been redirected to a null handle.
> >

Patch here: http://sourceware.org/ml/insight/2007-q2/msg00020.html

Can anyone please take a look at this?  Using insight on Cygwin without
this is a very frustrating affair which involves having to dismiss *two*
stupid focus-stealing pop-up dialogs every single time you type 'run'.

Brian


  reply	other threads:[~2007-06-25 21:48 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           ` Brian Dessent [this message]
2007-06-25 23:40             ` [patch ping^2] " 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
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=46803846.F99470AE@dessent.net \
    --to=brian@dessent.net \
    --cc=gdb-patches@sourceware.org \
    --cc=insight@sourceware.org \
    /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