From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: 3.0.7(0.338/5/3): Possible reference to Developer's instances of dev files in deployed build
Date: Thu, 05 Dec 2019 19:16:00 -0000 [thread overview]
Message-ID: <20191205191648.GC5146@calimero.vinschen.de> (raw)
In-Reply-To: <04da8ce9-0163-8381-644f-cc7c0f81a5f5@cornell.edu>
[-- Attachment #1: Type: text/plain, Size: 2108 bytes --]
On Dec 5 16:10, Ken Brown wrote:
> On 12/5/2019 7:52 AM, Corinna Vinschen wrote:
> > On Dec 5 10:18, Corinna Vinschen wrote:
> >> On Dec 4 21:41, Ken Brown wrote:
> >>> The difference is that NtCreateFile doesn't fail with
> >>> STATUS_OBJECT_NAME_NOT_FOUND in the other cases, so the code containing the
> >>> assertion doesn't get run.
> >>>
> >>> BTW, I just tried the following on my system:
> >>>
> >>> $ ls z:\\
> >>> ls: cannot access 'z:\': No such file or directory
> >>>
> >>> strace shows that NtCreateFile fails with STATUS_OBJECT_PATH_NOT_FOUND in this
> >>> case, so again the code containing the assertion is not run.
> >>>
> >>> To be continued...
> >>
> >> So, maybe we could just check if ext_here - path > 2, i. e.
> >>
> >> if (status == STATUS_OBJECT_NAME_NOT_FOUND && ext_here - path > 2)
> >>
> >> That excludes "X:" paths from this special handling for DOS-only drives.
> >
> > The only problem here is that I can't reproduce the assertion failure.
> >
> > I created a Samba share on a Linux machine, mounted it as drive Z:,
> > and set the "always available offline" property of the drive.
> >
> > After syncing I accessed the drive, then I stopped Samba on the Linux
> > server to switch the drive into offline mode. Then I ran `ls -la
> > /cygdrive/z'. After a few secs I got the offline content cached on the
> > local machine. I also tried `ls -la /cygdrive/' and `cd /cygdrive; ls
> > -la', but every time I got the expected output. In the cases I tried
> > to list /cygdrive itself I got the expected output, all drives except
> > the z drive.
> >
> > I tried this with Cygwin 3.1.0-0.8.x86_64 on Windows 7 and Windows 10.
> >
> > So either there's something very special in Wilfed's setup, or I'm
> > doing something wrong. Which is it?
>
> How does your strace output compare to Wilfed's when you list /cygdrive? Does
> it show a failed attempt to list Z: with an error from NtCreateFile?
Not at all. The strace doesn't show any attempt to open Z:.
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-12-05 19:16 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 21:03 Wilfed Olaf Sulla via cygwin
2019-12-04 21:41 ` Ken Brown
2019-12-05 9:18 ` Corinna Vinschen
2019-12-05 12:52 ` Corinna Vinschen
2019-12-05 16:10 ` Ken Brown
2019-12-05 19:16 ` Corinna Vinschen [this message]
2019-12-05 19:44 ` Ken Brown
2019-12-06 2:11 ` Norton Allen
2019-12-06 9:31 ` Corinna Vinschen
2019-12-08 21:50 ` Andrey Repin
2019-12-09 10:22 ` Corinna Vinschen
-- strict thread matches above, loose matches on Subject: below --
2019-12-10 13:37 Wilfed Olaf Sulla via cygwin
2019-12-10 18:57 ` Ken Brown
2019-12-11 0:09 ` Corinna Vinschen
2019-12-11 5:43 ` Ken Brown
2019-12-11 16:03 ` Corinna Vinschen
2019-12-06 12:35 Wilfed Olaf Sulla via cygwin
2019-12-06 4:56 Wilfed Olaf Sulla via cygwin
2019-12-06 11:07 ` Corinna Vinschen
2019-12-06 14:35 ` Corinna Vinschen
2019-12-07 21:03 ` Ken Brown
2019-12-09 9:20 ` Corinna Vinschen
2019-12-09 13:05 ` Ken Brown
2019-12-09 17:29 ` Corinna Vinschen
2019-12-10 8:44 ` Ken Brown
2019-12-04 17:18 Wilfed Olaf Sulla via cygwin
2019-12-04 18:22 ` Corinna Vinschen
2019-12-04 19:27 ` Wilfed Olaf Sulla via cygwin
2019-12-04 20:50 ` Ken Brown
2019-12-04 10:41 Wilfed Olaf Sulla via cygwin
2019-12-04 14:40 ` Ken Brown
2019-12-04 16:19 ` Wilfed Olaf Sulla via cygwin
2019-12-04 16:39 ` Ken Brown
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=20191205191648.GC5146@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).