Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Neal E. Coombes" <nealc@trdlnk.com>
To: gdb@sources.redhat.com
Subject: dbxread.c:1771: internal-error: sect_index_data not initialized
Date: Wed, 17 Sep 2003 15:02:00 -0000	[thread overview]
Message-ID: <3F687799.5050201@trdlnk.com> (raw)

A colleague of mine has found this bug (which I will also make a bug 
report for).  I'm really writing to this list because I'd like to help 
however I can to make gdb 6 suitable for us.

Currently in our development environtment all versions of gdb 5.0 and 
greater have show stopping bugs for us, and gdb 4 doesn't support gcc 3 
(and we don't want to switch back to gcc 2).

We've frozen our compiler at gcc 3.2.3 as it seems stable and able to do 
everything we need.  We'd like to freeze our debugger, but haven't been 
able to yet.  Please help me help gdb by giving me guidance on what more 
I can do.

Before I file the bug report, look below and let me know what other 
information may be relevant.  I'll try in the mean time to write a small 
program that still demonstrates the bug.

Thanks for all help,

Neal E. Coombes

Bug follows:

gdb 5.3.92 compiled with gcc 3.2.3 configured as i386-pc-solaris2.8
This bug only seems to occur with programs using gtkmm and gtkmm-2.0

GNU gdb 5.3.92
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain 
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-pc-solaris2.8"...

(gdb)
(gdb) b main
Breakpoint 1 at 0x81c8315: file main.C, line 133.
(gdb) r
Starting program: /home/lex/HEAD/apps/strategyViewer/strategyViewer
dbxread.c:1771: internal-error: sect_index_data not initialized
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)


             reply	other threads:[~2003-09-17 15:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-17 15:02 Neal E. Coombes [this message]
2003-09-17 17:54 ` Jim Blandy
2003-09-17 18:17   ` Andrew Cagney
2003-09-17 20:16     ` Neal E. Coombes
2003-09-18 22:41       ` Jim Blandy
2003-09-19 14:04         ` Neal E. Coombes
2003-09-18 22:34     ` Jim Blandy
2003-09-18 22:57       ` Andrew Cagney
2003-09-18 23:12         ` Jim Blandy
2003-09-19 19:45           ` Andrew Cagney
2003-09-17 17:54 Michael Elizabeth Chastain

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3F687799.5050201@trdlnk.com \
    --to=nealc@trdlnk.com \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox