This is the mail archive of the
mailing list for the Cygwin project.
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
On Fri, Nov 15, 2019 at 10:34 AM Brian Inglis
> On 2019-11-15 08:12, Keith Christian wrote:
> > On Fri, Nov 15, 2019 at 7:40 AM Ken Brown wrote:
> >> 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?
> $ TZ=UTC ls -glo --full /bin/tar
> -rwxr-xr-x 1 424979 2016-12-09 03:57:55.000000000 +0000 /bin/tar
> so not a recent Cygwin update.
> >> Works for me. Could you have some anti-virus software that's interfering? Look
> >> for suspicious DLLs in the strace output.
> > These are the DLL's in the strace output, expanded with "ldd." I
> > don't see anything out of the ordinary.
> > Is there a list of DLL's known to cause problems with Cygwin?
> > How would I better isolate the problem causing DLL? Specific verbiage
> > in the strace output? Should I run strace with the "-a" option?
> This is normal output:
> $ ldd /bin/tar
> ntdll.dll => /proc/cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll (0x7ff93d530000)
> KERNEL32.DLL => /proc/cygdrive/c/WINDOWS/System32/KERNEL32.DLL
> KERNELBASE.dll => /proc/cygdrive/c/WINDOWS/System32/KERNELBASE.dll
> cygwin1.dll => /usr/bin/cygwin1.dll (0x180040000)
> cygiconv-2.dll => /usr/bin/cygiconv-2.dll (0x3d8c50000)
> cygintl-8.dll => /usr/bin/cygintl-8.dll (0x3c8230000)
> > 1 CRYPTBASE.DLL =>
> > 4 RPCRT4.dll => /cygdrive/c/WINDOWS/System32/RPCRT4.dll
> > (0x7fff46070000)
> > 5 SYSFER.DLL => /cygdrive/c/WINDOWS/System32/SYSFER.DLL
> > (0x5a0b0000)
> > 6 advapi32.dll =>
> > /cygdrive/c/WINDOWS/System32/advapi32.dll (0x7fff45530000)
> > 7 bcryptPrimitives.dll =>
> > /cygdrive/c/WINDOWS/System32/bcryptPrimitives.dll (0x7fff44020000)
> > 8 bcryptprimitives.dll =>
> > /cygdrive/c/WINDOWS/System32/bcryptprimitives.dll (0x7fff44020000)
> > 11 msvcrt.dll => /cygdrive/c/WINDOWS/System32/msvcrt.dll
> > (0x7fff444c0000)
> > 13 psapi.dll => /cygdrive/c/WINDOWS/System32/psapi.dll
> > (0x7fff44790000)
> > 14 rpcrt4.dll => /cygdrive/c/WINDOWS/System32/rpcrt4.dll
> > (0x7fff46070000)
> > 15 sechost.dll =>
> SYSFER.DLL is Broadcom/Symantec Endpoint Protection (SEP) AV/BLODA, which pulls
> in all this other stuff, including MS VC RT, to clash with Cygwin, while
> reporting back to corporate, hogging CPU and I/O to do so, slowing your system
> to a crawl.
> Uninstall it, bypass checking under the Cygwin tree, or don't use Cygwin.
> If you feel a need for protection, Windows Defender is adequate; most AV
> products are overkill, and kill system performance.
> If this is in an org, complain (to your and their manager/VP) about the
> interference stopping you doing your work, and make them fix it, so they
> remember to do so in future, otherwise you may have problems and have to
> complain and wait every time they upgrade.
> Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
Thanks very much for the information. I should have run "strings" on
all of the DLL's and then I would have seen that.
This is a corporate PC so little chance of doing any uninstalls or modification.
At least I know why now, and you've given me some ideas about troublesome DLL's.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple