Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: muller@ics.u-strasbg.fr, gdb-patches@sourceware.org
Subject: Re: [RFC] Improve testsuite for poor expect behavior
Date: Wed, 17 Jun 2009 17:25:00 -0000	[thread overview]
Message-ID: <E1MGysh-00009o-EV@fencepost.gnu.org> (raw)
In-Reply-To: <20090617145429.GB7582@adacore.com> (message from Joel Brobecker 	on Wed, 17 Jun 2009 07:54:29 -0700)

> X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
> 	version=3.1.0
> Date: Wed, 17 Jun 2009 07:54:29 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> 
> > +#ifdef _WIN32
> > +  /* A Cygwin ssh session may not look like a terminal to the Windows
> > +     runtime; ensure unbuffered output.  */
> > +  setvbuf (stdout, NULL, _IONBF, BUFSIZ);
> > +  setvbuf (stderr, NULL, _IONBF, BUFSIZ);
> > +#endif
> 
> We have the exact same piece of code in our tree as well. We chose
> to put it in event-top, but it doesn't really matter.  I'd really
> like to see at least this part being committed.

Did someone check that switching it to binary will not interfere with
Emacs 23 GDB interface on Windows?


  reply	other threads:[~2009-06-17 17:25 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12 23:00 Pierre Muller
2009-06-13 14:52 ` Doug Evans
2009-06-13 15:05 ` Daniel Jacobowitz
2009-06-13 20:29   ` Pierre Muller
2009-06-13 23:55     ` 'Daniel Jacobowitz'
2009-06-14  0:25       ` Joel Brobecker
2009-06-15  7:23         ` Pierre Muller
2009-06-16 14:58           ` Joel Brobecker
2009-06-16 23:29             ` Pierre Muller
2009-06-17 13:36               ` 'Daniel Jacobowitz'
2009-06-17 14:54                 ` Joel Brobecker
2009-06-17 17:25                   ` Eli Zaretskii [this message]
2009-06-17 19:39                     ` Joel Brobecker
2009-06-18 14:38                       ` Eli Zaretskii
2009-06-18 14:59                         ` Joel Brobecker
2009-06-18 15:25                           ` Eli Zaretskii
2009-06-18 15:33                             ` Joel Brobecker
2009-06-18 15:58                               ` Samuel Bronson
2009-06-18 23:02                               ` Eli Zaretskii
2009-06-17 17:17                 ` Eli Zaretskii
2009-06-17 20:17                   ` Pierre Muller
2009-06-17 21:00                     ` Pierre Muller
2009-06-18 14:33                     ` Eli Zaretskii
2009-06-18 15:57                       ` Pierre Muller
2009-06-18 16:08                         ` Pedro Alves
2009-06-18 23:18                           ` Eli Zaretskii
2009-06-18 16:19                         ` Pedro Alves
2009-06-17 21:56                   ` Pierre Muller
2009-06-18 14:48                     ` Eli Zaretskii
2009-06-17 22:39                 ` Pierre Muller
2009-06-17 22:43                   ` 'Daniel Jacobowitz'
2009-06-17 22:54                     ` Pierre Muller
2009-06-17 23:21                       ` 'Daniel Jacobowitz'
2009-06-17 23:18                     ` Joel Brobecker
2009-06-18  6:31                       ` Mark Kettenis
2009-06-23 18:14               ` Joel Brobecker

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=E1MGysh-00009o-EV@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=muller@ics.u-strasbg.fr \
    /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