From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Regression in latest snapshot (x86 arch)?
Date: Tue, 20 Feb 2018 11:25:00 -0000 [thread overview]
Message-ID: <7c57af5b8908819821b73f4df6b3bb7a@xs4all.nl> (raw)
L.S.,
As far as I can tell, the latest snapshot (2018-02-16) has a problem in
case
of the x86 arch.
I noticed it when I applied "cp -p" to cygwin1.dll
@@ stat cygwin1.dll
File: cygwin1.dll
Size: 3003413 Blocks: 2936 IO Block: 65536 regular file
Device: 33d91880h/869865600d Inode: 15762598695825794 Links: 1
Access: (0755/-rwxr-xr-x) Uid: ( 1000/ Henri) Gid: ( 513/ None)
Access: 1970-01-01 01:01:39.427244800 +0100
Modify: 1970-01-01 01:00:54.998366800 +0100
Change: 2018-02-20 11:41:41.747593600 +0100
Birth: 2018-02-20 10:49:55.031336800 +0100
For some reason 'access time' and 'modify time' default to 1970-01-01. I
do
not notice this for the x86_64 arch.
Anybody NOT experiencing this "regression?"
Henri
@@ uname -a
CYGWIN_NT-6.1-WOW Seven 2.10.1(0.325/5/3) i686 Cygwin
@@ strings /usr/bin/cygwin1.dll | grep -m1 -E
'/vinschen/|/corinna/|/cygheap\.cc'
/ext/build/mknetrel/src/cygwin-snapshot-20180216-1/winsup/cygwin/cygheap.cc
@@ pwd
/home/Henri
@@ rm aap noot
@@ touch aap
@@ stat aap
File: aap
Size: 0 Blocks: 0 IO Block: 65536 regular
empty file
Device: 33d91880h/869865600d Inode: 5629499534242193 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 1000/ Henri) Gid: ( 513/ None)
Access: 1970-01-01 00:58:52.-659927900 +0100
Modify: 1970-01-01 00:58:52.-659927900 +0100
Change: 2018-02-20 12:19:28.967976100 +0100
Birth: 2018-02-20 12:19:28.967976100 +0100
@@ cp -p .bashrc noot
@@ stat noot
File: noot
Size: 8309 Blocks: 12 IO Block: 65536 regular file
Device: 33d91880h/869865600d Inode: 20829148276589133 Links: 1
Access: (0755/-rwxr-xr-x) Uid: ( 1000/ Henri) Gid: ( 513/ None)
Access: 1970-01-01 00:57:45.-158186600 +0100
Modify: 1970-01-01 00:57:45.-158186600 +0100
Change: 2018-02-20 12:01:52.670520600 +0100
Birth: 2017-05-24 19:42:17.311494900 +0200
@@ stat .bashrc
File: .bashrc
Size: 8309 Blocks: 12 IO Block: 65536 regular file
Device: 33d91880h/869865600d Inode: 37717646879229026 Links: 1
Access: (0755/-rwxr-xr-x) Uid: ( 1000/ Henri) Gid: ( 513/ None)
Access: 2018-01-24 15:27:52.646229400 +0100
Modify: 2018-01-24 15:27:52.646229400 +0100
Change: 2018-01-24 15:27:52.677429500 +0100
Birth: 2016-07-19 14:31:42.953010600 +0200
=====
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2018-02-20 11:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 11:25 Houder [this message]
2018-02-20 14:24 ` Houder
2018-02-20 14:44 ` Corinna Vinschen
2018-02-20 14:43 ` 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=7c57af5b8908819821b73f4df6b3bb7a@xs4all.nl \
--to=houder@xs4all.nl \
--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).