From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: tar 1.29 hangs, when run with strace, it exits with "illegal instruction"
Date: Thu, 08 Aug 2019 03:33:00 -0000 [thread overview]
Message-ID: <b9ea23d3-3ba7-f4eb-0f77-73c6cebaece9@SystematicSw.ab.ca> (raw)
In-Reply-To: <CAFWoy7Feu05w0G=PLtwr1160sME8EVFvn57kNdCwxL3_phgzdg@mail.gmail.com>
On 2019-08-07 12:20, Keith Christian wrote:
> I am able to run "tar ft somefile.tar" successfully on a Linux
> machine, same tar version (1.29.)
>
> This version hangs up the terminal, does not respond to Ctrl-C or
> Ctrl-Z, and terminates with an illegal instruction to the screen, not
> reflected in the strace output.
>
> File cygwin_tar_1_29_illegal_instruction.txt is attached with strace
> output, version, and "cygcheck tar" output.
Works just fine for me:
$ tar ft Downloads/nam.dist.tar
README
demo/
...
You may have some http://www.cygwin.com/acronyms/#BLODA interfering like an AV.
The strace shows tar fails in sysfer.dll, which is part of Symantec Endpoint
Protection CMC Firewall Application and Device Control, badly written from the
number of complaints about it, and as usual with these control and monitoring
products, they greatly slow down systems and interfere with work.
Deinstall SEP or bypass your cygwin directories.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
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 prev parent reply other threads:[~2019-08-08 3:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 18:21 Keith Christian
2019-08-08 3:33 ` Brian Inglis [this message]
2019-08-09 19:13 ` Keith Christian
2019-08-09 20:42 ` 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=b9ea23d3-3ba7-f4eb-0f77-73c6cebaece9@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).