public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Cygwin /usr/bin/stat returns "Birth: -", which value in FILE_BASIC_INFORMATION.CreationTime causes that?
Date: Thu, 4 Apr 2024 18:54:46 -0600	[thread overview]
Message-ID: <31e79a62-2068-4488-9195-b9e7abf716e3@SystematicSW.ab.ca> (raw)
In-Reply-To: <CANH4o6O=kbNTptDMNOvg6+HBYTufNgv_71Be2Fn6E3w7+qprVg@mail.gmail.com>

On 2024-04-04 18:05, Martin Wege via Cygwin wrote:
> I have problems with debugging, so a quick help would be appreciated,
> as I cannot figure this out after several hours of digging.
> 
> Cygwin /usr/bin/stat returns "Birth: -" for some files. Which value
> must the CreationTime member of FILE_BASIC_INFORMATION have to cause
> /usr/bin/stat ti return "-"? 0, -1, or something else?

https://git.savannah.gnu.org/cgit/coreutils.git/tree/src/stat.c#n1618

=> tv_nsec < 0

https://cygwin.com/git?p=newlib-cygwin.git;a=blob;f=winsup/cygwin/fhandler/disk_file.cc#l414

https://cygwin.com/git/?p=newlib-cygwin.git;a=blob;f=winsup/cygwin/times.cc#l283

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer     but when there is no more to cut
                                 -- Antoine de Saint-Exupéry

  reply	other threads:[~2024-04-05  0:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05  0:05 Martin Wege
2024-04-05  0:54 ` Brian Inglis [this message]
2024-04-05  1:08   ` Martin Wege
2024-04-05 15:51     ` Brian Inglis
2024-04-05  2:26 ` Win32 FILE_BASIC_INFORMATION.*Time.QuadPart - which value should be used if filesystem does not support it, so Cygwin /usr/bin/stat lists the value as '-'? Martin Wege
2024-04-09 21:14   ` Corinna Vinschen
2024-04-10  4:30     ` Brian Inglis
2024-04-10  7:59       ` 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=31e79a62-2068-4488-9195-b9e7abf716e3@SystematicSW.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).