From: Roumen Petrov <bugtrack@roumenpetrov.info>
To: cygwin@cygwin.com
Subject: Re: pipe hang issue when running as SYSTEM
Date: Fri, 25 Mar 2022 09:48:49 +0200 [thread overview]
Message-ID: <c5c3735f-40d7-1b03-6a00-01a232e2ed9d@roumenpetrov.info> (raw)
In-Reply-To: <20220325144253.4053d19d7e7b0243dcefa79e@nifty.ne.jp>
Hi,
Takashi Yano wrote:
> [SNIP]
>> Just got another report to MSYS2 of this behavior, this time from a Gitlab
>> CI runner that is running as a service and trying to pipe output from
>> Microsoft cl.exe while running configure. This user reports that 3.3.4
>> with your "[PATCH v2] Cygwin: pipe: Avoid deadlock for non-cygwin writer."
>> applied to it does not solve the problem.
>>
>> https://github.com/msys2/MSYS2-packages/issues/2893
> I can confirm the sample script hangs indeed if the script is
> running as SYSTEM account. However, in my test, the patch solves
> the issue.
>
> It would be very helpfull if a simple github repository with
> github actions, which can reproduce the issue, is provided.
In my environment with AD user account:
$ cmd.exe /c "type big_file" | :
The process tried to write to a nonexistent pipe.
$ cat big_file | :
*** starting debugger for pid NNN tid KKKKK
$ uname -a
CYGWIN_NT-10.0 ZZZZZZZ 3.3.4(0.341/5/3) 2022-01-31 19:35 x86_64 Cygwin
Remarks:
- no way to debug
- no error if run as administrator
Regards,
Roumen Petrov
prev parent reply other threads:[~2022-03-25 7:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 18:45 Jeremy Drake
2022-03-22 10:18 ` Takashi Yano
2022-03-22 13:17 ` Takashi Yano
2022-03-25 3:42 ` Jeremy Drake
2022-03-25 5:42 ` Takashi Yano
2022-03-25 7:09 ` Jeremy Drake
2022-03-25 11:11 ` Takashi Yano
2022-03-25 17:01 ` Jeremy Drake
2022-03-29 9:11 ` Takashi Yano
2022-03-25 7:48 ` Roumen Petrov [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=c5c3735f-40d7-1b03-6a00-01a232e2ed9d@roumenpetrov.info \
--to=bugtrack@roumenpetrov.info \
--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).