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
Created attachment 678633 [details] File: core_backtrace
Created attachment 678634 [details] File: environ
Created attachment 678635 [details] File: backtrace
Created attachment 678636 [details] File: limits
Created attachment 678637 [details] File: cgroup
Created attachment 678638 [details] File: smolt_data
Created attachment 678639 [details] File: executable
Created attachment 678640 [details] File: maps
Created attachment 678641 [details] File: dso_list
Created attachment 678642 [details] File: proc_pid_status
Created attachment 678643 [details] File: var_log_messages
Created attachment 678644 [details] File: open_fds
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.
It still happens with mdbtools-0.6-0.11.cvs20051109.fc18.1.x86_64.
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.
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.