Bug 107870 - GDB throws 'internal-error: sect_index_text not initialized' when debugging
GDB throws 'internal-error: sect_index_text not initialized' when debugging
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: gdb (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Alexandre Oliva
Jay Turner
Depends On:
  Show dependency treegraph
Reported: 2003-10-23 17:29 EDT by Peter Faltaous
Modified: 2015-01-07 19:06 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-12-30 08:54:48 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Eclipse failure. (3.05 KB, image/png)
2006-12-30 08:53 EST, Jan Kratochvil
no flags Details

  None (edit)
Description Peter Faltaous 2003-10-23 17:29:18 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030716

Description of problem:
When I use gdb to debug eclipse on x86_64, trying to step through some of the
methods causes the following:

internal-error: sect_index_text not initialized
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Ignore SIGPWR and SIGXCPU using 'handle'
2.Use gdb to debug the eclipse source code on x86_64, set a breakpoint  at
3.Use next or step to move through the code, eventually you receive this error


Actual Results:  I get the above mentioned error

Expected Results:  The debugging session should continue without error.

Additional info:
Comment 1 Jan Kratochvil 2006-12-30 08:53:56 EST
Created attachment 144577 [details]
Eclipse failure.

Tried to reproduce on RHEL3U8.x86_64.
Oldest / time-relevant Eclipse I found in Brew was `eclipse-2.1.2-5.x86_64.rpm'
(Apr 22 2004).
But still it did not run - see the attached error.
On the other hand even RHEL3 gdb is now gdb-6.3 based and I am sorry but I
would rather fix it only if it gets reported for something >= RHEL4 again.

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