Bug 895341

Summary: [abrt] mdbtools-0.6-0.10.cvs20051109.fc17.1: __memcpy_ssse3_back: Process /usr/bin/mdb-export was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Cristian Ciupitu <cristian.ciupitu>
Component: mdbtoolsAssignee: Hans de Goede <hdegoede>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: hdegoede
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:e3c340130d1b9bf02a4b6e160fb1e0745289ca6d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 14:51:12 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: core_backtrace
none
File: environ
none
File: backtrace
none
File: limits
none
File: cgroup
none
File: smolt_data
none
File: executable
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: var_log_messages
none
File: open_fds none

Description Cristian Ciupitu 2013-01-15 04:20:48 UTC
Description of problem:
mdb-export seems to crash when exporting a sensitive table (named tblLicense). I don't know exactly what's with that table nor the database because it's used by a 3rd party program.

Version-Release number of selected component:
mdbtools-0.6-0.10.cvs20051109.fc17.1

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        mdb-export ../MicroShopPro.mcs tblLicense
crash_function: __memcpy_ssse3_back
kernel:         3.6.10-2.fc17.x86_64

truncated backtrace:
:Thread no. 1 (3 frames)
: #0 __memcpy_ssse3_back at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1579
: #1 memcpy at /usr/include/bits/string3.h:52
: #2 mdb_ole_read at data.c:519

Comment 1 Cristian Ciupitu 2013-01-15 04:20:50 UTC
Created attachment 678633 [details]
File: core_backtrace

Comment 2 Cristian Ciupitu 2013-01-15 04:20:53 UTC
Created attachment 678634 [details]
File: environ

Comment 3 Cristian Ciupitu 2013-01-15 04:20:55 UTC
Created attachment 678635 [details]
File: backtrace

Comment 4 Cristian Ciupitu 2013-01-15 04:20:57 UTC
Created attachment 678636 [details]
File: limits

Comment 5 Cristian Ciupitu 2013-01-15 04:20:59 UTC
Created attachment 678637 [details]
File: cgroup

Comment 6 Cristian Ciupitu 2013-01-15 04:21:01 UTC
Created attachment 678638 [details]
File: smolt_data

Comment 7 Cristian Ciupitu 2013-01-15 04:21:03 UTC
Created attachment 678639 [details]
File: executable

Comment 8 Cristian Ciupitu 2013-01-15 04:21:06 UTC
Created attachment 678640 [details]
File: maps

Comment 9 Cristian Ciupitu 2013-01-15 04:21:08 UTC
Created attachment 678641 [details]
File: dso_list

Comment 10 Cristian Ciupitu 2013-01-15 04:21:10 UTC
Created attachment 678642 [details]
File: proc_pid_status

Comment 11 Cristian Ciupitu 2013-01-15 04:21:12 UTC
Created attachment 678643 [details]
File: var_log_messages

Comment 12 Cristian Ciupitu 2013-01-15 04:21:14 UTC
Created attachment 678644 [details]
File: open_fds

Comment 13 Fedora End Of Life 2013-07-03 22:35:52 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 14 Cristian Ciupitu 2013-07-03 23:38:01 UTC
It still happens with mdbtools-0.6-0.11.cvs20051109.fc18.1.x86_64.

Comment 15 Fedora End Of Life 2013-12-21 10:23:02 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 16 Fedora End Of Life 2014-02-05 14:51:16 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.