From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Bash heredoc on FD 3
Date: Tue, 08 Jan 2019 21:05:00 -0000 [thread overview]
Message-ID: <20190108210534.GI593@calimero.vinschen.de> (raw)
In-Reply-To: <20190108112705.GF593@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 2409 bytes --]
On Jan 8 12:27, Corinna Vinschen wrote:
> On Jan 7 16:19, Steven Penny wrote:
> > On Mon, 7 Jan 2019 20:03:13, Corinna Vinschen wrote:
> > > I can't reproduce this with my latest code. It works fine for me
> > > every time, independently of POSIXLY_CORRECT.
> > >
> > > I uploaded new snapshots to https://cygwin.com/snapshots/ with all
> > > the latest changes. Please try again.
> >
> > I retested with cygwin1-20190107.dll.xz. My results below. Note that "success"
> > means that with Bash, the script runs without error, regardless of
> > "POSIXLY_CORRECT" variable as you said. "failure" is to mean that with Bash,
> > running with "POSIXLY_CORRECT" produces this error:
> >
> > awk: error: can't open source file `/dev/fd/3' for reading (Permission
> > denied)
> >
> > Windows 10: success
> > Windows 8.1: failure
> > Windows 7: failure
> > [...]
>
> I could reproduce this on W8.1. After some debugging it turned out that
> this is, in fact, not related to POSIXLY_CORRECT at all.
>
> POSIXLY_CORRECT only changes the way the file is used in gawk. If
> POSIXLY_CORRECT isn't set, it just uses the incoming file descriptor 3
> due to some code handling the path "/dev/fd/<descriptor>" differently.
> This works fine under all circumstances because it does not trigger my
> new code for /proc/<pid>/fd/<descriptor> at all.
>
> However, as soon as POSIXLY_CORRECT is set, my new code is triggered and
> falls flat on its face on pre-W10 systems (serves me right for
> developing and testing on W10 only). The reason is that file delete
> semantics have changed on W10. On pre-W10, reopening a file by handle
> (equivalent to the Win32 API call ReOpenFile) does not work on files for
> which the delete dispostion has been set. This works fine on W10,
> though.
>
> Back to the drawing board. I have an idea or two how to workaround this
> shortcoming of pre-W10 systems.
>
> Just FTR, I really like what MSFT changes in W10 under the hood. I'm
> especially happy that the changes for WSL are exposed to the Windows
> subsystem, too, so we can profit from them as well. Personally I'm
> not looking back to pre-W10 systems at all.
I added some changes to make this work in older systems as well.
I uploaded new snapshots to //cygwin.com/snapshots/
Please try.
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-01-08 21:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-02 18:43 Steven Penny
2018-12-03 15:43 ` cyg Simple
2018-12-03 15:56 ` cyg Simple
2018-12-03 17:28 ` Eliot Moss
2018-12-04 12:13 ` Houder
2018-12-04 14:22 ` cyg Simple
2018-12-05 6:55 ` Houder
2019-01-06 20:18 ` Corinna Vinschen
2019-01-07 18:28 ` Steven Penny
2019-01-07 19:03 ` Corinna Vinschen
2019-01-08 0:19 ` Steven Penny
2019-01-08 11:27 ` Corinna Vinschen
2019-01-08 21:05 ` Corinna Vinschen [this message]
2019-01-09 0:17 ` Steven Penny
2019-01-09 9:48 ` Corinna Vinschen
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=20190108210534.GI593@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).