Red Hat Bugzilla – Bug 1016849
[abrt] abiword-2.8.6-22.fc19: __gnu_cxx::__verbose_terminate_handler: Process /usr/bin/abiword was killed by signal 6 (SIGABRT)
Last modified: 2013-12-02 16:00:17 EST
Description of problem:
I tried to open a rather large docx file. Abiword flashed a window and then disappeared. I did not try opening with abiword again.
Version-Release number of selected component:
cmdline: abiword /home/x4s/SCALE_62_Manual/C09tsunami-3d.docx
runlevel: N 5
var_log_messages: Oct 8 15:34:12 xncse3 abrt: Saved core dump of pid 28001 (/usr/bin/abiword) to /var/tmp/abrt/ccpp-2013-10-08-15:34:11-28001 (30527488 bytes)
Thread no. 1 (10 frames)
#2 __gnu_cxx::__verbose_terminate_handler at ../../../../libstdc++-v3/libsupc++/vterminate.cc:95
#3 __cxxabiv1::__terminate at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:38
#4 std::terminate at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:48
#5 __cxxabiv1::__cxa_throw at ../../../../libstdc++-v3/libsupc++/eh_throw.cc:84
#6 std::__throw_logic_error at ../../../../../libstdc++-v3/src/c++11/functexcept.cc:64
#7 std::string::_S_construct<char const*> at /usr/src/debug/gcc-4.8.1-20130603/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/bits/basic_string.tcc:133
#8 _S_construct_aux<char const*> at /usr/src/debug/gcc-4.8.1-20130603/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/bits/basic_string.h:1725
#9 _S_construct<char const*> at /usr/src/debug/gcc-4.8.1-20130603/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/bits/basic_string.h:1746
#10 std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string at /usr/src/debug/gcc-4.8.1-20130603/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/bits/basic_string.tcc:215
#11 OXML_Element_Field::OXML_Element_Field at OXML_Element_Field.cpp:32
Created attachment 809508 [details]
Created attachment 809509 [details]
Created attachment 809510 [details]
Created attachment 809511 [details]
Created attachment 809512 [details]
Created attachment 809513 [details]
Created attachment 809514 [details]
Created attachment 809515 [details]
Created attachment 809516 [details]
libgsf-1.14.28-1.fc19,abiword-3.0.0-4.fc19,sugar-write-94-1.fc19 has been submitted as an update for Fedora 19.
Package libgsf-1.14.28-1.fc19, abiword-3.0.0-4.fc19, sugar-write-94-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libgsf-1.14.28-1.fc19 abiword-3.0.0-4.fc19 sugar-write-94-1.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Packages for abiword and libgsf have been in updates-testing for a couple of days now, but the sugar-write package isn't there yet. If it doesn't get there before noon tomorrow, it will be another week before I can test it.
libgsf-1.14.28-1.fc19, abiword-3.0.0-4.fc19, sugar-write-94-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
I updated to libgsf-1.14.28-1.fc19, abiword-3.0.0-4.fc19, sugar-write-94-1.fc19 this morning, and the problem still occurs. Abiword is either writing a backup file, or has just finished writing the file when it crashes. The original file is in binary, but is ~7% larger than the backup file abiword writes. The crash is apparently 100% reproducible.