abrt version: 1.1.13 architecture: x86_64 Attached file: backtrace cmdline: /usr/lib64/openoffice.org3/program/soffice.bin '/tmp/Daily log 14_09_2010.xlsx' comment: I don't believe any (relevant) Fedora updates were installed since the system was up. component: openoffice.org crash_function: elf_dynamic_do_rela executable: /usr/lib64/openoffice.org3/program/soffice.bin kernel: 2.6.34.7-56.fc13.x86_64 package: openoffice.org-brand-1:3.2.0-12.31.fc13 rating: 4 reason: Process /usr/lib64/openoffice.org3/program/soffice.bin was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) time: 1286265212 uid: 578 How to reproduce ----- 1. Just start ooffice (with or without argument) 2. 3.
Created attachment 451600 [details] File: backtrace
Does this happen every time, or did it just happen once ? Looks odd, I'd like to either blame glibc or claim that the .sos have become corrupt on disk.
It happened a few times after each other. I haven't rebooted yet (lots of work open currently). Just after posting this bug 'abrt' itself crashed with the same error. dmesg: soffice.bin[4257]: segfault at 7fae4f045ee6 ip 0000003b1960b538 sp 00007fffd3422120 error 4 in ld-2.12.1.so[3b19600000+1e000] python[4411]: segfault at 3d259d3ee6 ip 0000003b1960b538 sp 00007fff79865390 error 4 in ld-2.12.1.so[3b19600000+1e000] rpm -V glibc shows no errors.
With multiple apps dying in elf_dynamic_do_rela in ld.so this shouldn't be assigned to OOo anyway. Sounds like there's some generic bustage here.
I agree, but I wasn't aware of that at the moment of reporting this issue. I'll check if things still go wrong after rebooting and file a bug report at the proper place if so. Thanks for helping.
Please attach `readelf -r /usr/lib64/openoffice.org3/program/../basis-link/program/gconfbe1.uno.so'.
Created attachment 451617 [details] Output of readelf -r /usr/lib64/openoffice.org3/program/../basis-link/program/gconfbe1.uno.so
Something has randomly overwritten memory.
I wasn't able to reproduce this issue. The next day, even without rebooting, oo started up normally again. Probably a suspend to ram/resume caused libc to be reloaded in ram.
Can't reproduce it myself, *shrug*.