From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22834 invoked by alias); 17 Sep 2003 17:54:56 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 22827 invoked from network); 17 Sep 2003 17:54:56 -0000 Received: from unknown (HELO concert.shout.net) (204.253.184.25) by sources.redhat.com with SMTP; 17 Sep 2003 17:54:56 -0000 Received: from duracef.shout.net (duracef.shout.net [204.253.184.12]) by concert.shout.net (8.12.9/8.12.9) with ESMTP id h8HHst1W020956; Wed, 17 Sep 2003 12:54:55 -0500 Received: from duracef.shout.net (localhost [127.0.0.1]) by duracef.shout.net (8.12.9/8.12.9) with ESMTP id h8HHstHK001084; Wed, 17 Sep 2003 12:54:55 -0500 Received: (from mec@localhost) by duracef.shout.net (8.12.9/8.12.9/Submit) id h8HHst9f001083; Wed, 17 Sep 2003 13:54:55 -0400 Date: Wed, 17 Sep 2003 17:54:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200309171754.h8HHst9f001083@duracef.shout.net> To: gdb@sources.redhat.com, nealc@trdlnk.com Subject: Re: dbxread.c:1771: internal-error: sect_index_data not initialized X-SW-Source: 2003-09/txt/msg00216.txt.bz2 neal> Before I file the bug report, look below and let me know what other neal> information may be relevant. I'll try in the mean time to write a small neal> program that still demonstrates the bug. Thanks for asking! It does not matter very much what version of gcc was used to compile gdb. It matters much more what version of gcc was used to compile the *test program*, because that determines the information in the executable program which gcc actually reads. Also the version of binutils matters (ld --version or as --version). gdb 5.3.92 / gcc 3.2.3 is a fine configuration to file bug reports against. Your script excerpt is perfect for a bug report. It helps to attach a copy of the test program executable. In fact this is even more useful than the source code of the test program. Please run 'ldd' and report the shared libraries that your test program uses in the body of the bug report. If there is a lot of info in the bug report, you can make a directory on your machine. Drop in your source code, executable file, a Makefile (if you want), typescript files, README's, whatever. Then make a tarball of that and use that for an attachment. Thanks, Michael C GDB QA Guy