| Summary: | Cannot report empathy crash | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Christopher Beland <beland> | ||||
| Component: | abrt | Assignee: | Denys Vlasenko <dvlasenk> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rawhide | CC: | anton, dvlasenk, iprikryl, jmoskovc, kklic, mtoman, npajkovs | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | abrt-2.0.4.981-1.fc16 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-10-03 18:02:14 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Christopher Beland
2011-04-08 14:48:44 UTC
(In reply to comment #0) > The resulting ABRT backtrace reads: > > >>> > Missing separate debuginfo for > Try: yum --disablerepo='*' --enablerepo='*-debuginfo' install > /usr/lib/debug/.build-id/25/7d0d6467b9f4374470e0384a3e602be99b058e > /var/cache/abrt-di/usr/lib/debug/.build-id/25/7d0d6467b9f4374470e0384a3e602be99b058e > [New Thread 2099] > [New Thread 13257] > [New Thread 2102] > [Thread debugging using libthread_db enabled] > Core was generated by `empathy'. > Program terminated with signal 6, Aborted. > #0 __kernel_vsyscall () at arch/x86/vdso/vdso32/int80.S:16 > 16 ret > > Timeout exceeded: 60 second, killing gdb > <<< Unfortunately, this is inevitable. There are (and will be) coredumps on which gdb hangs/enters infinite loop when it tries to generate a backtrace. ABRT will kill gdb in such cases. > Clicking the Refresh button resulted in the below output in the dialog box, but > failed to produce anything more useful. It took many seconds to run, and it > looked like it was mostly doing nothing: > > >>> > Analyzing corefile: /var/spool/abrt/ccpp-1302184661-2099/coredump > Searching the missing debuginfo packages > To download: (0.00) M / Installed size: 0.00 M > Complete! > Generating backtrace > Starting the debuginfo installation > Analyzing corefile: /var/spool/abrt/ccpp-1302184661-2099/coredump > Searching the missing debuginfo packages > [HANGS FOR SEVERAL SECONDS] > To download: (0.00) M / Installed size: 0.00 M > Complete! > Generating backtrace > <<< ...and we had a bug where ABRT sometimes _failed_ to kill gdb. So it can hang indefinitely, or until gdb crashes on oom or stack overflow. This is now fixed. I guess we need to at least recommend users to file a gdb bug in this case. I am updating the message: - strbuf_append_strf(buf_out, "\nTimeout exceeded: %u seconds, killing %s\n"... + strbuf_append_strf(buf_out, + "\nTimeout exceeded: %u seconds, killing %s\n" + "Looks like gdb hung while generating backtrace.\n" + "This may be a bug in gdb. Consider submitting a bug report\n" + "to gdb developers. Please attach coredump to the bug report if you do\n"... Pushed to git: commit 9c6f6678f8158b56c16825499f334f37544299c4 Author: Denys Vlasenko <dvlasenk> Date: Fri Jul 15 15:37:05 2011 +0200 abrt-2.0.4.981-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/abrt-2.0.4.981-1.fc16 Package abrt-2.0.4.981-1.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing abrt-2.0.4.981-1.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/abrt-2.0.4.981-1.fc16 then log in and leave karma (feedback). abrt-2.0.4.981-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |