Bug 519296 - gdb assertion errors, unable to debug cores
Summary: gdb assertion errors, unable to debug cores
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gdb
Version: rawhide
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Jan Kratochvil
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-26 00:36 UTC by Andrew Hecox
Modified: 2009-08-26 05:19 UTC (History)
1 user (show)

Fixed In Version: gdb-6.8.50.20090818-5.fc12
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-08-26 05:19:33 UTC


Attachments (Terms of Use)
gdb core (4.38 MB, application/x-lzma)
2009-08-26 00:38 UTC, Andrew Hecox
no flags Details

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.


Note You need to log in before you can comment on or make changes to this bug.