Bug 1096131
| Summary: | gdb painfully slow to show backtrace of libreoffice crashes | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | matti aarnio <matti.aarnio> |
| Component: | gdb | Assignee: | Jan Kratochvil <jan.kratochvil> |
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | chris+rhbugzilla, gbenson, jan.kratochvil, palves, patrickm, pmuldoon, sergiodj |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-05-29 12:59:53 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1103894 | ||
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 this bug is closed as described in the policy above. 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. Sourceware bugzilla issue has been fixed. Libreoffice has not crashed as of late on me so I have not had change to validate the backtrace production. If it persists at F21/F22, another bug can be issued. (In reply to matti aarnio from comment #2) > Sourceware bugzilla issue has been fixed. > Libreoffice has not crashed as of late on me so I have not had change to > validate the backtrace production. > > If it persists at F21/F22, another bug can be issued. You can still obtain a backtrace from LibreOffice (or any other program) by (e.g.) attaching to the running process. You just need to obtain the PID of the process, and then issue a "gdb program PID". |
Description of problem: Encountered a bug at libreoffice, got abrt to do back-trace. Have loaded all debuginfo files that gdb asks for. Running simple "where" takes very long time because of two things: - gdb loads first all debuginfo files into memory and in this particular case there are very large amounts of that data - guess: internal data structures looking it up are inefficient, and therefore each back-trace step takes several minutes of memory searching (or file IO?) to locate particular line of debuginfo. ( libreoffice-debuginfo 688 MB, installed size: 2.8 GB. ) Version-Release number of selected component (if applicable): gdb-7.6.50.20130731-19.fc20.x86_64 How reproducible: Every time I look at libreoffice back-traces with full symbol sets. If I throw away libreoffice-debuginfo, then back-trace production is fast, but usefulness is less. Additional info: This machine has 16 GB RAM, no swap is happening. I would use "gcc -pg" version of gdb to see where it really spends all that time, but don't have time myself to debug it more..