public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: fstat st_size on open files on Parallels filesystem is wrong
Date: Wed, 04 Nov 2015 09:45:00 -0000	[thread overview]
Message-ID: <20151104094540.GA23227@calimero.vinschen.de> (raw)
In-Reply-To: <22073.42807.638243.560521@compute03.cs.columbia.edu>

[-- Attachment #1: Type: text/plain, Size: 1610 bytes --]

On Nov  4 01:35, Jonathan Lennox wrote:
> On Tuesday, November 3 2015, "Corinna Vinschen" wrote to "cygwin@cygwin.com" saying:
> 
> > Btw., there's more than one problem here.  The fact that all drives
> > have the same volume name *and* a serial number of 0 leads to all
> > drives being identified as the same drive.  I have to add some code
> > creating a reproducible serial number from scratch if the original
> > serial number is 0, but for testing, I didn't implement this yet.
> 
> I've confirmed that this is the case for all the prlsf drives I have (drives
> U:-Z:).
> 
> > Talking about testing.  I created a test DLL which provides a lot
> > of output when stracing the calls.  I'll send you a private mail
> > with the URL to this DLL in a minute.  Please install it, and under
> > that DLL, run
> > 
> >   $ strace -o stat.trace ./stat-size-test.exe /cygdrive/y/foo
> > 
> > I'll need to have a look into that strace to (hopefully) see what's
> > going wrong.
> 
> Attached.

Thanks, but...  are you sure you created this with the test DLL I sent
you the URL for?  The attached strace looks like stock Cygwin.  It
doesn't contain any of the additional strace output the DLL is supposed
to generate and some of it is in a code path you can't avoid when
calling functions on files.

I'll upload a new DLL to the URL I mentioned in PM in a minute, just to
be sure I didn't screw this up myself.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-11-04  9:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-21 18:27 lennox
2014-04-21 18:35 ` Andrey Repin
2014-04-21 18:46   ` lennox
2014-04-22  8:16     ` Corinna Vinschen
2014-04-22 16:09       ` lennox
2014-04-22 20:57       ` lennox
2014-04-23  8:41         ` Corinna Vinschen
2014-04-23 16:47           ` lennox
2014-04-23 17:24             ` Corinna Vinschen
2015-10-08 16:16               ` Jonathan Lennox
2015-10-21 11:07                 ` Corinna Vinschen
2015-11-02  9:38                   ` Jonathan Lennox
2015-11-02 11:23                     ` Corinna Vinschen
2015-11-02 13:08                       ` Jonathan Lennox
2015-11-02 14:06                         ` Corinna Vinschen
2015-11-02 22:05                           ` Jonathan Lennox
2015-11-03 12:19                             ` Corinna Vinschen
2015-11-04  6:35                               ` Jonathan Lennox
2015-11-04  9:45                                 ` Corinna Vinschen [this message]
2015-11-02 12:52                     ` cyg Simple

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=20151104094540.GA23227@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).