From: Eli Zaretskii <eliz@gnu.org>
To: Ken Brown <kbrown@cornell.edu>
Cc: 25854@debbugs.gnu.org
Subject: bug#25854: 26.0.50; tramp-test19-directory-files-and-attributes fails on 32-bit Cygwin
Date: Fri, 24 Feb 2017 09:55:33 +0200 [thread overview]
Message-ID: <83y3wwrpje.fsf@gnu.org> (raw)
In-Reply-To: <c0086021-f9c3-2aaf-8c29-798bc32fac66@cornell.edu> (message from Ken Brown on Thu, 23 Feb 2017 18:19:50 -0500)
> From: Ken Brown <kbrown@cornell.edu>
> Date: Thu, 23 Feb 2017 18:19:50 -0500
>
> Starting with commit 3a6df2d,
> tramp-test19-directory-files-and-attributes fails on 32-bit Cygwin. The
> reason is that inode numbers tend to be very large, on the order of
> 10^17, at least on my systems. As a result, the "convert inode" code in
> tramp-convert-file-attributes always falls back to tramp-get-inode.
> Since this increments by 1 on every call, the file-attribute comparisons
> in tramp-test19-directory-files-and-attributes always fail.
>
> The significance of commit 3a6df2d is that it makes
> tramp-get-remote-stat return a non-nil value, so that tramp uses 'stat'
> for file attributes; this returns the true (large) inode number. Prior
> to that commit, tramp-get-remote-stat would always return nil, so that
> the tramp-perl-file-attributes script would be used for file
> attributes. This script uses whatever inode number is returned by
> Perl's version of 'stat', which is presumably some sort of 32-bit
> truncation of the true inode number.
>
> Although I'm seeing this on 32-bit Cygwin, it seems to me that it could
> in principle happen on any 32-bit platform.
Would it work to convert the large inode values to a float?
next prev parent reply other threads:[~2017-02-24 7:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 23:19 bug#25854: 26.0.50; tramp-test19-directory-files-and-attributes fails on 32-bit Cygwin Ken Brown
2017-02-24 7:55 ` Eli Zaretskii [this message]
2017-02-24 7:59 ` Eli Zaretskii
2017-02-24 14:04 ` Michael Albinus
2017-02-24 14:49 ` Ken Brown
2017-02-24 15:45 ` Ken Brown
2017-02-24 16:02 ` Michael Albinus
2017-02-25 14:05 ` Michael Albinus
2017-02-25 15:19 ` 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=83y3wwrpje.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25854@debbugs.gnu.org \
--cc=kbrown@cornell.edu \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.