Bug 618526 - [abrt] crash in cpio-2.10-6.fc13: memcpy: Process /bin/cpio was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in cpio-2.10-6.fc13: memcpy: Process /bin/cpio was killed by sig...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: cpio
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ondrej Vasik
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:eb82bf65ef0e03a0e9b481961f3...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-27 08:00 UTC by Andreas Berendsen
Modified: 2010-10-20 12:24 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-10-20 12:24:22 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (17.51 KB, text/plain)
2010-07-27 08:00 UTC, Andreas Berendsen 		no flags Details
View All

Description Andreas Berendsen 2010-07-27 08:00:31 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: cpio -pdv /store/music/
component: cpio
crash_function: memcpy
executable: /bin/cpio
global_uuid: eb82bf65ef0e03a0e9b481961f38d38c434c8853
kernel: 2.6.33.6-147.fc13.x86_64
package: cpio-2.10-6.fc13
rating: 4
reason: Process /bin/cpio was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 Andreas Berendsen 2010-07-27 08:00:34 UTC 
Created attachment 434619 [details]
File: backtrace
Comment 2 Ondrej Vasik 2010-08-31 13:51:54 UTC 
I'm not able to reproduce it with similar file(same size, same blocks)... is this issue reproducible? Could it be corrupted source file? What is the filesystem on the source side? Filesize of that vob file is not that big ... only 1.07G ... strange...
Please provide more information how to reproduce that... TIA.
Comment 3 Ondrej Vasik 2010-10-20 12:24:22 UTC 
I'm sorry, but as it is in needinfo for more than one month, I'm closing this bugzilla INSUFFICIENT_DATA. I'm not able to reproduce the issue on my system with provided reproducer.

Feel free to reopen the issue once you provide information requested in comment #2 and explain the reproducer more clearly(or provide reproducer archive)...
Note You need to log in before you can comment on or make changes to this bug.