This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 2/3] Unbuffer stdout and stderr in cygwin
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Thu, 01 Aug 2013 19:36:58 +0300
- Subject: Re: [PATCH 2/3] Unbuffer stdout and stderr in cygwin
- References: <1375087546-22591-1-git-send-email-yao at codesourcery dot com> <1375087546-22591-3-git-send-email-yao at codesourcery dot com> <83siyxxtif dot fsf at gnu dot org> <51FA16C6 dot 6010006 at codesourcery dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Thu, 1 Aug 2013 16:05:26 +0800
> From: Yao Qi <yao@codesourcery.com>
> CC: <gdb-patches@sourceware.org>
>
> On 07/29/2013 11:42 PM, Eli Zaretskii wrote:
> > I would suggest to call the function using_cygwin_pty or some such.
> > "is_in_cygwin" is IMO too ambiguous.
> >
>
> OK, fixed in patch 1/3.
Thanks.
> Yes, I get your point. GDB would be less efficient on output. How
> about this patch? still unbuffering stdout and stderr, due to these
> regression?
Apart of the change in the function's name, nothing else changed,
right?