From: Frank Middleton <f.middleton@apogeect.com>
To: Hui Zhu <teawater@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Experiences building and using gdb 6.8 on Solaris
Date: Thu, 30 Apr 2009 15:41:00 -0000 [thread overview]
Message-ID: <49F9BB0E.4010706@apogeect.com> (raw)
In-Reply-To: <daef60380904292244p625d5f72n4d59b67751b2c3a@mail.gmail.com>
On 04/30/09 01:44, Hui Zhu wrote:
> Hi Frank,
>
> Could you try your issue with gdb-cvs-head version?
> You can get it in ftp://sourceware.org/pub/gdb/snapshots/current/ .
>
> Thanks,
> Hui
Still seems to fail...
gdb a.out
GNU gdb (GDB) 6.8.50.20090427-cvs
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "sparc-sun-solaris2.11".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
(gdb) r
Starting program: /tmp/a.out
elfread.c:433: 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)
next prev parent reply other threads:[~2009-04-30 14:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 0:26 Frank Middleton
2009-04-27 5:25 ` Paul Pluzhnikov
2009-04-27 18:18 ` Frank Middleton
2009-04-30 0:12 ` Paul Pluzhnikov
2009-04-30 0:35 ` Frank Middleton
2009-04-30 5:44 ` Paul Pluzhnikov
2009-04-30 14:52 ` Frank Middleton
2009-04-30 8:02 ` Hui Zhu
2009-04-30 15:41 ` Frank Middleton [this message]
2009-04-30 16:18 ` Paul Pluzhnikov
2009-04-30 16:20 ` Frank Middleton
2009-04-30 16:56 ` Paul Pluzhnikov
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=49F9BB0E.4010706@apogeect.com \
--to=f.middleton@apogeect.com \
--cc=gdb@sourceware.org \
--cc=teawater@gmail.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