This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Unbuffer stdout and stderr on windows
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: palves at redhat dot com, gdb-patches at sourceware dot org, yao at codesourcery dot com
- Date: Tue, 13 Aug 2013 17:05:29 -0700
- Subject: Re: [PATCH] Unbuffer stdout and stderr on windows
- References: <1374462417-7961-1-git-send-email-yao at codesourcery dot com> <838v0yy556 dot fsf at gnu dot org> <51EE23F8 dot 1070905 at codesourcery dot com> <83wqohw4ee dot fsf at gnu dot org> <20130729192559 dot GA5348 at ednor dot casa dot cgf dot cx> <83d2q1xiyv dot fsf at gnu dot org> <51F6C7B2 dot 3020400 at redhat dot com> <20130731034045 dot GA5565 at ednor dot casa dot cgf dot cx> <20130812211105 dot GA11128 at adacore dot com> <8361v9piop dot fsf at gnu dot org>
> Yes, Emacs does that. But it is never a problem in that case, because
> it's the user who looks at the results, not a program that wants to
> interpret them.
[...]
> I think this problem is only relevant to the test suite,
Actually, I did find that having stdout and stderr mixed up to
be very confusing. But I know I've never found a solution that
would be acceptable to everyone. This is why I've never formally
submitted the patch, only published it as an FYI the few times
someone asked about the issue. Credits to Dan Jacobowitz, btw,
for giving it to me in the first place.
> program tries to interpret the output and trips on extraneous
> characters. Let's not make the solution so much wider than the
> problem. With Yao's patch, you now have this in a Cygwin terminal;
> can we leave all the other types alone, please?
Sure. I don't see how this is going to help the testsuite, but
Yao's patch is already progress, and we've been using a vendor patch
for years anyway, so we can continue doing so without problems.
--
Joel