Re: [PATCH] Unbuffer stdout and stderr on windows

Pedro Alves
2013-08-16T14:21:57Z

On 08/16/2013 03:03 PM, Eli Zaretskii wrote:

> I suggest not to broaden the issue beyond the original problem, lest
> we will be unable to solve it.

Nobody's doing that. What I'm saying is that the testsuite is not
special, and we should _zone in_ to the real problem, and fix it
completely. Making output not buffered seems to do that, assuming
GDB doesn't output half a line to stdout, then output to stderr, and
then output the rest to stderr, which very much it will want to avoid,
given stderr is unbuffered on most systems. If the output is buffered, then
something must be forcing flushes to get the same effect. Fixing
the issue for the testsuite but not for other GDB-consumers that
spawn it in a pipe, with special modes is just not the right
solution, IMO. What will probably happen with that solution is
that Windows GDB clients will end up using the special testsuite-only
flag too, because by default, GDB will remain broken... Why add
a flag for a half-fix instead of fixing the issue completely?

--
Pedro Alves