public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: "/usr/bin/tar.exe" hangs, Windows 10, CYGWIN_NT-10.0 3.0.7(0.338/5/3) 2019-04-30 18:08 x86_64
Date: Fri, 15 Nov 2019 15:13:00 -0000	[thread overview]
Message-ID: <f97280c1-c841-1f45-f608-cd6ae50c5ce7@cornell.edu> (raw)
In-Reply-To: <CAFWoy7EzOt5dXBB6=LQz0zVEVYD6FMQeANW6VasXT2onn+pDrw@mail.gmail.com>

On 11/15/2019 9:19 AM, Keith Christian wrote:
> Tar in recent updates to Cygwin64 hangs.
> 
> When the tar command is run with strace, it generates voluminous
> output but won't list tar file contents or extract the tar file (or
> tar.gz, tar.xz, etc.)
> 
> tar --version
> tar (GNU tar) 1.29
> Packaged by Cygwin (1.29-1)
> Copyright (C) 2015 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> 
> Written by John Gilmore and Jay Fenlason.
> 
> ls -l /usr/bin/tar.exe
> -rwxr-xr-x 1 kchris0000 Domain Users 424979 Dec  8  2016 /usr/bin/tar.exe
> 
> 
> Could someone check this please?

Works for me.  Could you have some anti-virus software that's interfering?  Look 
for suspicious DLLs in the strace output.

Ken

--
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:[~2019-11-15 14:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15 14:40 Keith Christian
2019-11-15 15:13 ` Ken Brown [this message]
2019-11-15 15:30   ` Keith Christian
2019-11-15 17:34     ` Ken Brown
2019-11-15 18:39     ` Brian Inglis
2019-11-15 22:25       ` Keith Christian
2019-11-16 13:39         ` ASSI
2019-11-16 18:40           ` Brian Inglis

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=f97280c1-c841-1f45-f608-cd6ae50c5ce7@cornell.edu \
    --to=kbrown@cornell.edu \
    --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).