From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: yao@codesourcery.com, gdb-patches@sourceware.org, brobecker@adacore.com
Subject: Re: [PATCH] Unbuffer stdout and stderr on windows
Date: Fri, 16 Aug 2013 14:57:00 -0000 [thread overview]
Message-ID: <83mwohn0nj.fsf@gnu.org> (raw)
In-Reply-To: <520E357E.6080803@redhat.com>
> Date: Fri, 16 Aug 2013 15:21:50 +0100
> From: Pedro Alves <palves@redhat.com>
> CC: yao@codesourcery.com, gdb-patches@sourceware.org, brobecker@adacore.com
>
> 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.
A complete solution, if it exists, might require much more effort,
which is IMO unjustified in the absence of complaints.
> 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...
I use the Emacs client all the time, and I don't think it's broken.
> Why add a flag for a half-fix instead of fixing the issue
> completely?
I fear that we don't know/understand enough to do TRT for the complete
solution. The "half-fix", OTOH, solves a well-defined issue that is
understood very well.
next prev parent reply other threads:[~2013-08-16 14:57 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 3:07 Yao Qi
2013-07-22 15:41 ` Eli Zaretskii
2013-07-23 6:35 ` Yao Qi
2013-07-23 17:52 ` Eli Zaretskii
2013-07-29 19:26 ` Christopher Faylor
2013-07-29 19:30 ` Christopher Faylor
2013-07-29 19:30 ` Eli Zaretskii
2013-07-29 19:51 ` Pedro Alves
2013-07-31 3:40 ` Christopher Faylor
2013-08-12 21:11 ` Joel Brobecker
2013-08-13 17:28 ` Christopher Faylor
2013-08-13 18:08 ` Eli Zaretskii
2013-08-14 0:05 ` Joel Brobecker
2013-08-15 17:36 ` Christopher Faylor
2013-08-15 17:44 ` Eli Zaretskii
2013-08-15 17:59 ` Christopher Faylor
2013-08-15 18:44 ` Eli Zaretskii
2013-08-16 11:46 ` Pedro Alves
2013-08-16 12:34 ` Yao Qi
2013-08-16 13:20 ` Eli Zaretskii
2013-08-16 13:37 ` Pedro Alves
2013-08-16 14:03 ` Eli Zaretskii
2013-08-16 14:21 ` Pedro Alves
2013-08-16 14:57 ` Eli Zaretskii [this message]
2013-08-16 15:10 ` Pedro Alves
2013-08-16 15:24 ` Pedro Alves
2013-08-16 15:43 ` Eli Zaretskii
2013-08-16 16:41 ` Christopher Faylor
2013-08-16 15:41 ` Eli Zaretskii
2013-08-22 6:14 ` Yao Qi
2013-08-22 14:18 ` Joel Brobecker
2013-08-23 2:20 ` Yao Qi
2013-08-23 13:38 ` Joel Brobecker
2013-08-27 20:39 ` Pedro Alves
2013-08-28 7:23 ` Yao Qi
2013-08-28 9:39 ` Pedro Alves
2013-08-28 12:25 ` Yao Qi
2013-08-16 13:17 ` Eli Zaretskii
2013-08-16 13:30 ` Pedro Alves
2013-08-16 13:42 ` Eli Zaretskii
2013-08-16 14:13 ` Pedro Alves
2013-08-16 14:44 ` Eli Zaretskii
2013-08-16 15:05 ` Pedro Alves
2013-08-16 15:13 ` Eli Zaretskii
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=83mwohn0nj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=yao@codesourcery.com \
/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