From: Volker Quetschke <quetschke@scytek.de>
To: cygwin@cygwin.com
Subject: tar: Child died with signal 13
Date: Tue, 26 Feb 2002 02:54:00 -0000 [thread overview]
Message-ID: <3C7B6591.9040503@scytek.de> (raw)
Hi,
recently I found a problem when I try to untar some tar.gz archives
under cygwin. The tar.gz at this link is ca. 1,5kb
http://www.scytek.de/expat.pat.tar.gz .
It is just one example, it is taken from OpenOffice641C.
On my Windows 2K machine, cygwin updatet a few minutes ago, I get:
Administrator@LISI ~/tartest
$ tar -tzf expat.pat.tar.gz
pat/
pat/xmlparse/
pat/xmlparse/hashtable.h.pat
pat/xmlparse/xmlparse.h.pat
pat/xmltok/
tar: Child died with signal 13
tar: Error exit delayed from previous errors
Administrator@LISI ~/tartest
$ la
total 6
dr-xr-xr-x 2 Administ Kein 0 Feb 26 10:02 .
drwxr-xr-x 6 Administ Kein 4096 Feb 26 10:02 ..
-r-xr-xr-x 1 Administ Kein 1435 Sep 20 2000 expat.pat.tar.gz
I get this error in both cases, with CYGWIN=ntsec tty and CYGWIN=tty.
I also get this error on Cygwin on our Windows 2K server, but there I
can't change the environement ;-)
If I do an gunzip first, and then a tar -tf foo.tar I get no error.
I also don't get an error doing the tar -tzf on cygwin on Windows98SE
or Linux.
Only few *.tar.gz files have this problem, but some have. I have three
more examples, but they are not so short as the one mentioned above.
Any ideas?
Volker
--
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2002-02-26 10:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 2:54 Volker Quetschke [this message]
2002-02-26 6:14 ` Eugene Rosenzweig
2002-02-27 10:41 ` Volker Quetschke
2002-03-04 2:06 ` Max Bowsher
2002-02-28 7:42 ` Randall R Schulz
2002-03-01 6:47 ` Volker Quetschke
2002-03-01 7:29 ` Randall R Schulz
2002-03-01 8:29 ` Volker Quetschke
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=3C7B6591.9040503@scytek.de \
--to=quetschke@scytek.de \
--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).