Bug 740097

Summary: [abrt] tar-2:1.23-9.fc14: delete_archive_members: Process /bin/tar was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Dave Galloway <davematel>
Component: tarAssignee: Ondrej Vasik <ovasik>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: kdudka, ovasik
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:6cbf54f4da6adbba6b6e49ffee02c26508355ece
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-09-21 08:43:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Dave Galloway 2011-09-20 23:13:20 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 4464 bytes
cmdline: /bin/gtar --force-local --no-wildcards -v --delete -f /media/750Gig_USB/1tb_in_box_file.tar -- media/30f0ca80-943e-430c-960f-ba4912565d0c/02._750_Gig_lvm2_Saved/750_Gig_1_tar_extract_list.txt media/30f0ca80-943e-430c-960f-ba4912565d0c/02._750_Gig_lvm2_Saved/750_Gig_tar_extract_list.txt
component: tar
Attached file: coredump, 475136 bytes
crash_function: delete_archive_members
executable: /bin/tar
kernel: 2.6.35.14-96.fc14.x86_64
package: tar-2:1.23-9.fc14
rating: 4
reason: Process /bin/tar was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1316548582
uid: 500

How to reproduce
-----
1.I don't know
2.
3.
Comment 1 Dave Galloway 2011-09-20 23:13:23 UTC 
Created attachment 524103 [details]
File: backtrace
Comment 2 Ondrej Vasik 2011-09-21 08:43:50 UTC 
Thanks for report.

As the steps to reproduce are "I don't know" and this abort() call is just intended tar behaviour (in uncommon error conditions). It would be good to have a simple reproducer, to see why it reached the abort() call... 

Closing this report insufficient data (there is nothing to fix in tar anyway, maybe except some user friendly error message on exit...). Feel free to reopen the issue if you get some reproducer scenario.