Bug 519296

Summary: gdb assertion errors, unable to debug cores
Product: [Fedora] Fedora Reporter: Andrew Hecox <ahecox>
Component: gdbAssignee: Jan Kratochvil <jan.kratochvil>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: high    
Version: rawhideCC: jan.kratochvil
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: gdb-6.8.50.20090818-5.fc12 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-08-26 05:19:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
gdb core none

Description Andrew Hecox 2009-08-26 00:36:23 UTC
using F12 alpha 1, using gdb to analyze cores leads to numerous assertion errors, eg:

(gdb) bt
../../gdb/objfiles.c:828: internal-error: qsort_cmp: Assertion `sect1_addr >= obj_section_endaddr (sect2)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y

../../gdb/objfiles.c:828: internal-error: qsort_cmp: Assertion `sect1_addr >= obj_section_endaddr (sect2)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) y
Aborted (core dumped)

gdb cannot print the bt regardless of if the session is aborted or not.

Before I installed all the necessary debuginfo files for the core (gnome-terminal) I was analyzing, I was able to get a bt (with some unresolved line numbers).

Comment 1 Andrew Hecox 2009-08-26 00:38:54 UTC
Created attachment 358651 [details]
gdb core

Comment 2 Jan Kratochvil 2009-08-26 05:19:33 UTC
Already workarounded now.