Hide Forgot
Description of problem: When I try to delete a file from a gzipped archive, tar dumps a core (with signal 6) and exits. Version-Release number of selected component (if applicable): ttar-1.15.1-30.el5.i386 gzip-1.3.5-11.el5.centos.1.i386 How reproducible: Steps to Reproduce: 1. open shell windows (xterm e.g.) 2. touch file1 file2; tar zcvf arc.tar.gz file1 file2 3. tar --delete -z -f arc.tar.gz file1 Actual results: Aborted (core dumped) Expected results: no output, no core. Additional info: 'gdb /bin/tar core...' prints: Program terminated with signal 6, Aborted. #0 0x0051d402 in __kernel_vsyscall () 'strace tar --delete -z -f arc.tar.gz file1' prints: ... open("/proc/mounts", O_RDONLY|O_LARGEFILE) = 3 ... read(3, "rootfs / rootfs rw 0 0\n/dev/root"..., 4096) = 1372 read(3, "", 4096) = 0 close(3) = 0 munmap(0xb7fa5000, 4096) = 0 clock_gettime(CLOCK_REALTIME, {1297077830, 180495161}) = 0 rt_sigaction(SIGCHLD, {SIG_DFL, [CHLD], SA_RESTART}, {SIG_DFL, [], 0}, 8) = 0 rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0 tgkill(22090, 22090, SIGABRT) = 0 --- SIGABRT (Aborted) @ 0 (0) --- +++ killed by SIGABRT (core dumped) +++
Thanks for report, `--append', `--concatenate', `--update`, and `--delete' commands do not work on compressed archives. That's expected behaviour and documented in info documentation. However, it would be better to just inform user that this operation is not supported than just dump core with assert() SIGABRT. RHEL-6 and current Fedora just informs user that tar "Cannot update compressed archives".
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Prior to this update, tar terminated with a core dump when trying to update a tar archive that was compressed using an external compression program. With this update, this problem has been corrected so that tar now displays an error message when trying to update this archive.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1449.html
*** Bug 773068 has been marked as a duplicate of this bug. ***