From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/3] Detect GDB is in cygwin
Date: Tue, 06 Aug 2013 03:05:00 -0000 [thread overview]
Message-ID: <520067CB.4000300@codesourcery.com> (raw)
In-Reply-To: <20130806020839.GA3362@ednor.casa.cgf.cx>
On 08/06/2013 10:08 AM, Christopher Faylor wrote:
> I'm saying that it looks like your code will detect "echo yes | gdb"
> as running on a cygwin pty.
In this case, the file name of handle looks like
"\cygwin-c5e39b7a9d22bafb-pipe-0xBC0-0x1". It is expected to return
true in this case too, that is to say, we need to set stdout/stderr
unbuffered in this case too.
In my test configuration, I use two "methods" to access remote Cygwin
respectively, one is "ssh" and the other is "ssh -t". We need these
changes on stdout/stderr for these two "methods".
See the code in my patch ...
> + /* Now check the name pattern. With pseudo-tty allocated in ssh,
> + the filename of handle of stdin looks like this:
> +
> + \cygwin-c5e39b7a9d22bafb-{p,t}ty1-from-master
This is the name pattern I get if I "ssh -t" to remote Cygwin.
> +
> + Without pseudo-tty allocated in ssh, the filename of handle of
> + stdin looks like this:
> +
> + \cygwin-c5e39b7a9d22bafb-pipe-0x14C8-0x3
This is the name patter I get if I "ssh" to remtoe Cygwin.
> +
> + If the file name is prefixed with "\cygwin-", GDB is running in
> + cygwin. */
> +
> + return (cp != NULL && wcsncmp (cp, L"\\cygwin-", 8) == 0);
We really need to return true for these two cases. I find it is
confusing to say "using pty" or "not using pty" in the comments, so I
choose "with pty allocated" or "without pty allocated", which is much
clear to me.
> +/* Return true if GDB is running in Cygwin pseudo-tty. */
> +
> +int
> +using_cygwin_pty (void)
Probably you are confused by the function name and the comments. Does
it below help?
/* Return true if GDB is running in Cygwin. */
int
using_cygwin (void)
--
Yao (é½å°§)
next prev parent reply other threads:[~2013-08-06 3:05 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 [this message]
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
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=520067CB.4000300@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