public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: Cygwin 2.8.1-1
Date: Fri, 21 Jul 2017 18:16:00 -0000	[thread overview]
Message-ID: <20170721142753.GC2185@dinwoodie.org> (raw)
In-Reply-To: <20170710082756.GC30071@calimero.vinschen.de>

On Mon, Jul 10, 2017 at 10:27:56AM +0200, Corinna Vinschen wrote:
> On Jul  7 16:07, Adam Dinwoodie wrote:
> > On Mon, Jul 03, 2017 at 03:31:22PM +0200, Corinna Vinschen wrote:
> > > I uploaded a new Cygwin release 2.8.1-1
> > 
> > This has introduced a regression that I'm seeing when running `ls` on
> > some network shares.  I can reproduce the behaviour with an install of
> > only the base Cygwin packages, and the behaviour disappears if I
> > downgrade back to v2.8.0-1.
> > 
> > <snip>
> 
> I have not been able to reproduce this.  The only relevant changes in
> 2.8.1 in terms of `ls' were related to reparse points (native symlinks,
> directory junctions, etc) and a change of st_blocks computation related
> to CompactOS compression.
> 
> For a start, can you please check if you can reproduce the problem
> with the devolper snapshot from 20170606?

After several false starts (including Windows getting very upset about
*something* to do with moving DLLs around and blue screening on me), I'm
not seeing this behaviour with the 20170606 snapshot.

> Also, can you reproduce this with 2.8.1 under strace perhaps? If so,
> I'd be interested to see the strace output.  If you fear to compromise
> company data, we can arrange to do this in private email.

I have the strace output from both the successful and unsuccessful
cases; the failing case on v2.8.1 appears to be going wrong at the
following exception, which appears to be the first significant
difference between the two strace outputs:

       47  268130 [main] ls 16232 stat_worker: (\??\UNC\<path>, 0x84, 0x180318898), file_attributes 2592
    --- Process 16232, exception c0000005 at 000000018012f3cd

If you can give me your private email address, I'll send the full strace
output over.

Thank you!

Adam

--
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

      reply	other threads:[~2017-07-21 14:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03 15:58 Corinna Vinschen
2017-07-07 15:07 ` Adam Dinwoodie
2017-07-10  8:28   ` Corinna Vinschen
2017-07-21 18:16     ` Adam Dinwoodie [this message]

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=20170721142753.GC2185@dinwoodie.org \
    --to=adam@dinwoodie.org \
    --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).