From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST: Cygwin 3.1.0-0.3
Date: Sat, 31 Aug 2019 04:21:00 -0000 [thread overview]
Message-ID: <20190831131814.2f6c9969a4380a457e61d91b@nifty.ne.jp> (raw)
In-Reply-To: <CALK-3mKnHy5tGzi4kkf7CZ4m-6x1fGwBsk=bc8Jv1KFoU_reHA@mail.gmail.com>
On Sat, 31 Aug 2019 02:51:34 +0530
Biswapriyo Nath wrote:
> On Friday, August 30, 2019, Takashi Yano <takashi.yano@nifty.ne.jp> wrote:
> The HPCON isn't a handle. It's a pointer of a struct of three handles. In
> my opinion, I think it's consistent with pty functions in libc. Like in
> forkpty(2) the pid is returned in master side, here HPCON is same.
Then, is it possible to DuplicateHanlde() for three handles in HPCON
to other process which calls ioctl() with new HPCON?
> Q: From which process do you want to access it?
Just a posibility. Some programs may open pty in a process, call
fork(), exit the process and call ioctl in the fork'ed process.
> To know more about the ConPTY internals here are two of my sample program:
>
> * XConPty: https://github.com/Biswa96/XConPty
> * wslbridge2: https://github.com/Biswa96/wslbridge2/tree/master/rawpty
Oh! Is that your work? I already know XConPty site and I wondered
what is this and how the auther knows such internal things.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-08-31 4:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 12:47 Corinna Vinschen
2019-08-29 16:51 ` Biswapriyo Nath
2019-08-30 8:11 ` Corinna Vinschen
2019-08-30 19:16 ` Takashi Yano
2019-08-30 20:21 ` Corinna Vinschen
2019-08-31 3:58 ` Biswapriyo Nath
2019-08-31 4:21 ` Takashi Yano [this message]
2019-09-01 6:32 ` Biswapriyo Nath
2019-09-02 8:17 ` Corinna Vinschen
2019-09-03 9:28 ` Biswapriyo Nath
2019-09-03 10:48 ` Corinna Vinschen
2019-09-05 18:11 ` Jim Reisert AD1C
2019-09-06 2:23 ` Ken Brown
2019-09-06 5:22 ` Jim Reisert AD1C
2019-09-06 10:03 ` Thomas Wolff
2019-09-07 3:32 ` Takashi Yano
2019-09-07 11:53 ` Thomas Wolff
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=20190831131814.2f6c9969a4380a457e61d91b@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).