This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: tar with switches leads to stack dump
- From: Eric Blake <ebb9 at byu dot net>
- To: fergus at bonhard dot uklinux dot net
- Cc: cygwin at cygwin dot com
- Date: Wed, 21 Dec 2005 06:03:29 -0700
- Subject: Re: tar with switches leads to stack dump
- References: <000001c60608$8ab30190$500210ac@tcgp.dundee.ac.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to fergus on 12/21/2005 1:28 AM:
> I'm trying to append several new files to an existing zipped .tar.gz and
> maintain the zipped format. I find that
> tar -vrzf exist.tar.gz *.new
> leads to an
> Aborted (core dumped)
> message. More than likely my syntax is faulty, but maybe not. (Creating a
> .tar.gz from scratch using "tar -vczf .." works fine. Appending new files to
> an existing .tar using "tar -vrf exist.tar *.new" works fine.) This happens
> with 1.5.18 and 1.5.19s 20051220. Please can anybody put me right or confirm
> the core dump? Thank you.
It looks like an upstream bug; and it has already been 'fixed' in CVS,
where it gives the error:
$ tar/src/tar -vrzf exist.tar.gz *.new
tar/src/tar: Cannot update compressed archives
Try `tar/src/tar --help' or `tar/src/tar --usage' for
more information.
I still don't see why upstream refuses to update a compressed archive, but
at least it didn't abort.
Thanks for the report; I'll get a new tar out as soon as I can locate and
backport the fix from CVS to 1.15.1 to avoid the abort().
- --
Life is short - so eat dessert first!
Eric Blake ebb9@byu.net
volunteer cygwin tar maintainer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDqVKh84KuGfSFAYARAi29AKCfr2CFntyeAw/sqXpjd3FdwZCGHQCeIQeM
GMs6UmlHCrszifiHjn9NBUc=
=s2ic
-----END PGP SIGNATURE-----
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/