From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/3] Detect GDB is in cygwin
Date: Fri, 16 Aug 2013 01:07:00 -0000 [thread overview]
Message-ID: <520D7AFC.9000507@codesourcery.com> (raw)
In-Reply-To: <20130815174010.GB6955@ednor.casa.cgf.cx>
On 08/16/2013 01:40 AM, Christopher Faylor wrote:
> You've already acknowledged that your code will decide to become
> unbuffered whether you are running on a cygwin pipe or cygwin pty. What
> is special about cygwin pipes that makes you want to make them
> unbuffered while ignoring normal Windows pipes?
In a cygwin session, I start gdb "./gdb", and stdin is a cygwin pty. If
I start gdb "echo yes | ./gdb", stdin is a cygwin pipe, right?
In a windows console (cmd.exe), if I start gdb "echo yes | ./gdb", stdin
is a windows pipe. Is it correct?
>
> Can you explain*why* you don't want to change the behavior on native
> windows?
because the problem this patch series want to address is not related to
native windows, so we don't want to change its behaviour. We think
"buffered/unbuffered" are user visible behaviour, and we should be
careful on changing them.
The original problem this patch series want to address is about testing
mingw32 native gdb in cygwin. This patch series can make
dejagnu/testsuite happy, and improve the test result dramatically
(without this patch series, the result is unusable at all).
If Pierre or some one else thinks we need changes here on native
windows, that is fine, let us do it. There are many issues for mingw,
cygwin and windows, and it is impossible to fix all of them in one patch
series. This patch series make some progresses and Pierre's incoming
RCF will make some progresses too, isn't it what we want?
>
> I really don't like having gdb rely on undocumented Cygwin behavior.
> You're introducing a tenuous dependency between the way Cygwin creates
> ptys and pipes which could easily break if we decide to change something
> in Cygwin.
GDB has been relying on undocumented behaviours here and there.
'grep "no.*document" *.c" may find some. If the file name pattern of
ptys and pipes are changed some day, we can update the code here to
match, which is not difficult, IMO.
On the other hand, do you think it is hard to get this documented in
Cygwin? in order to improve the interoperability between Cygwin and GDB.
--
Yao (é½å°§)
next prev parent reply other threads:[~2013-08-16 1:07 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 8:46 [PATCH 0/3 V3] Test mingw32 GDB " Yao Qi
2013-07-29 8:46 ` [PATCH 1/3] Detect GDB is " Yao Qi
2013-07-29 15:38 ` Eli Zaretskii
2013-07-30 9:27 ` Yao Qi
2013-07-30 15:33 ` Eli Zaretskii
2013-08-01 7:52 ` Yao Qi
2013-08-01 16:33 ` Eli Zaretskii
2013-08-02 2:51 ` Yao Qi
2013-08-02 6:10 ` Eli Zaretskii
2013-08-03 4:55 ` Christopher Faylor
2013-08-04 8:45 ` Yao Qi
2013-08-05 4:41 ` Christopher Faylor
2013-08-05 6:23 ` Yao Qi
2013-08-06 2:08 ` Christopher Faylor
2013-08-06 3:05 ` Yao Qi
2013-08-08 5:11 ` Christopher Faylor
2013-08-08 7:24 ` Yao Qi
2013-08-15 17:40 ` Christopher Faylor
2013-08-15 18:58 ` Tom Tromey
2013-08-15 19:14 ` Eli Zaretskii
2013-08-16 0:06 ` Yao Qi
2013-08-16 2:01 ` Tom Tromey
2013-08-16 1:07 ` Yao Qi [this message]
2013-08-16 16:37 ` Christopher Faylor
2013-08-08 7:28 ` Pierre Muller
2013-08-13 8:12 ` Yao Qi
2013-08-13 8:23 ` Pierre Muller
2013-07-29 8:46 ` [PATCH 2/3] Unbuffer stdout and stderr " Yao Qi
2013-07-29 15:42 ` Eli Zaretskii
2013-08-01 8:06 ` Yao Qi
2013-08-01 16:36 ` Eli Zaretskii
2013-08-02 0:40 ` Yao Qi
2013-07-29 8:46 ` [PATCH 3/3] Set stdin/stdout/stderr to binary mode " Yao Qi
2013-07-29 15:44 ` Eli Zaretskii
2013-08-01 8:10 ` Yao Qi
2013-08-01 16:37 ` Eli Zaretskii
2013-07-29 14:03 ` [PATCH 0/3 V3] Test mingw32 GDB " Pierre Muller
2013-07-30 6:03 ` Yao Qi
2013-07-29 18:03 ` Tom Tromey
2013-07-29 18:43 ` Eli Zaretskii
2013-08-13 9:35 [PATCH 0/3 V4] " Yao Qi
2013-08-13 9:35 ` [PATCH 1/3] Detect GDB is " Yao Qi
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=520D7AFC.9000507@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).