Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb@sources.redhat.com, nealc@trdlnk.com
Subject: Re: dbxread.c:1771: internal-error: sect_index_data not initialized
Date: Wed, 17 Sep 2003 17:54:00 -0000	[thread overview]
Message-ID: <200309171754.h8HHst9f001083@duracef.shout.net> (raw)

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


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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-17 17:54 Michael Elizabeth Chastain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-17 15:02 Neal E. Coombes
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

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=200309171754.h8HHst9f001083@duracef.shout.net \
    --to=mec@shout.net \
    --cc=gdb@sources.redhat.com \
    --cc=nealc@trdlnk.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