abrt version: 1.1.18
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
Attached file: coredump, 475136 bytes
reason: Process /bin/tar was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
How to reproduce
1.I don't know
Created attachment 524103 [details]
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.