From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin-developers@cygwin.com
Subject: Re: program will hang when dup and close fd opend by posix_openpt
Date: Fri, 15 Jan 2021 00:05:33 +0900 [thread overview]
Message-ID: <20210115000533.2f505196697741529c5740da@nifty.ne.jp> (raw)
In-Reply-To: <20210114183440.ac0068e5ed64675efe1e3294@nifty.ne.jp>
On Thu, 14 Jan 2021 18:34:40 +0900
Takashi Yano via Cygwin-developers <cygwin-developers@cygwin.com> wrote:
> On Thu, 14 Jan 2021 13:48:25 +0800
> Peiyuan Song via Cygwin-developers <cygwin-developers@cygwin.com> wrote:
> > dup will clone all info from `fhandler_pty_master` except pty master
> > control thread and pty master forwarding thread, when close that fd
> > the `fhandler_pty_master` heap will be reclaimed, but the thread run
> > on `fhandler_pty_master` object will not stop. when close duped fd,
> > those threads will access the reclaimed space and cause this issue.
>
> Thanks for the report. Let me consider.
I came up with a solution. I will submit a patch for this issue
together with other patches after testing a while.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
prev parent reply other threads:[~2021-01-14 15:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 5:48 Peiyuan Song
2021-01-14 9:34 ` Takashi Yano
2021-01-14 15:05 ` Takashi Yano [this message]
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=20210115000533.2f505196697741529c5740da@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin-developers@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).