Bug 740097 - [abrt] tar-2:1.23-9.fc14: delete_archive_members: Process /bin/tar was killed by signal 6 (SIGABRT)
Summary: [abrt] tar-2:1.23-9.fc14: delete_archive_members: Process /bin/tar was killed...
Alias: None
Product: Fedora
Classification: Fedora
Component: tar
Version: 14
Hardware: x86_64
OS: Unspecified
Target Milestone: ---
Assignee: Ondrej Vasik
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:6cbf54f4da6adbba6b6e49ffee0...
Depends On:
TreeView+ depends on / blocked
Reported: 2011-09-20 23:13 UTC by Dave Galloway
Modified: 2011-09-21 08:43 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-09-21 08:43:50 UTC

Attachments (Terms of Use)
File: backtrace (4.36 KB, text/plain)
2011-09-20 23:13 UTC, Dave Galloway
no flags Details

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
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

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.

Note You need to log in before you can comment on or make changes to this bug.