| Summary: | [abrt] gdb-7.3.50.20110722-10.fc16: free_cached_comp_units: Process /usr/bin/gdb was killed by signal 11 (SIGSEGV) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Guillaume Desmottes <gdesmott> | ||||||||||
| Component: | gdb | Assignee: | Jan Kratochvil <jan.kratochvil> | ||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 16 | CC: | jan.kratochvil, pmuldoon, qguo, sergiodj, tromey | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | x86_64 | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | abrt_hash:5eea7f862bbfe730b9ea7ed26f5cd00ea5062c9d | ||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2011-12-13 16:32:32 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
Guillaume Desmottes
2011-12-12 15:32:53 UTC
Created attachment 545777 [details]
File: dso_list
Created attachment 545778 [details]
File: maps
Created attachment 545779 [details]
File: environ
Created attachment 545780 [details]
File: backtrace
Do you have the problem reproducible?
It happened due to:
Dwarf Error: Cannot handle DW_FORM_<unknown> in DWARF reader [in module /usr/lib/debug/lib64/libc-2.14.90.so.debug]
While the crash should not happen even with invalid debuginfo files in reality currently GDB does not try to be safe against such cases.
It is more suspicious why you have glibc-debuginfo-2.14.90-21.x86_64 corrupted.
Could you try:
gdb -readnow /lib64/libc-2.14.90.so
I also do not see e02146cbd7b3747790cf4808baa58dc78c2e0042 in the build-id list, do you have Fedora /lib64/libc-2.14.90.so? What does say:
rpm -V glibc{,-debuginfo}
?
That works for me. If it works for you I suspect some hardware problems, run memtest86+ in such case.
(In reply to comment #5) > Do you have the problem reproducible? No, it happened just once. > It happened due to: > Dwarf Error: Cannot handle DW_FORM_<unknown> in DWARF reader [in module > /usr/lib/debug/lib64/libc-2.14.90.so.debug] > > While the crash should not happen even with invalid debuginfo files in reality > currently GDB does not try to be safe against such cases. > > It is more suspicious why you have glibc-debuginfo-2.14.90-21.x86_64 corrupted. > Could you try: > gdb -readnow /lib64/libc-2.14.90.so Reading symbols from /lib64/libc-2.14.90.so...Reading symbols from /usr/lib/debug/lib64/libc-2.14.90.so.debug...expanding to full symbols...done. expanding to full symbols...done. Seems to work. > I also do not see e02146cbd7b3747790cf4808baa58dc78c2e0042 in the build-id > list, do you have Fedora /lib64/libc-2.14.90.so? What does say: > rpm -V glibc{,-debuginfo} > ? I do have this file. $ rpm -V glibc{,-debuginfo} missing /usr/lib64/audit/sotruss-lib.so (Permission denied) ?........ /usr/sbin/glibc_post_upgrade.x86_64 ?........ /usr/sbin/glibc_post_upgrade.i686 > That works for me. If it works for you I suspect some hardware problems, run > memtest86+ in such case. Ok, I'll try that and let you know. Thanks but so far I do not see a GDB bug to fix. As long as I forgive: (In reply to comment #5) > While the crash should not happen even with invalid debuginfo files in reality > currently GDB does not try to be safe against such cases. (In reply to comment #6) > > That works for me. If it works for you I suspect some hardware problems, run > > memtest86+ in such case. > > Ok, I'll try that and let you know. Nope, no error found. |