This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/1384: mipsread.c:402: gdb-internal-error: sect_index_data not initialized
- From: david dot cote at certdgy dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 19 Sep 2003 18:46:03 -0000
- Subject: gdb/1384: mipsread.c:402: gdb-internal-error: sect_index_data not initialized
- Reply-to: david dot cote at certdgy dot com
>Number: 1384
>Category: gdb
>Synopsis: mipsread.c:402: gdb-internal-error: sect_index_data not initialized
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Fri Sep 19 18:48:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: David Cote
>Release: 5.3
>Organization:
>Environment:
OS Version: OSF1 p102 V5.1 732 alpha
GDB: This GDB was configured as "alphaev67-dec-osf5.1".
CC Version: Compaq C V6.3-029 on Compaq Tru64 UNIX V5.1 (Rev. 732) Compiler Driver V6.3-029 (sys) cc Driver
>Description:
(gdb) run
Starting program: /apps/pathways/dev/bin/pw_load
/apps/pathways/gnu/gdb-5.3/gdb/mipsread.c:402: gdb-internal-error: sect_index_data not initialized
An internal GDB error was detected. This may make further
debugging unreliable. Quit this debugging session? (y or n) y
Create a core file containing the current state of GDB? (y or n) n
>How-To-Repeat:
Happens every time gdb is initiated. I can provide a core
file if it would be helpful.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: