Re: Experiences building and using gdb 6.8 on Solaris

[Frank Middleton <f.middleton@apogeect.com>]

On 04/26/09 20:43, Paul Pluzhnikov wrote:

> First, you should verify that it is indeed libXau.so.6 that is causing
> the problem.

It would seem that it is

> /usr/local/bin/gdb a.out
GNU gdb 6.8
Copyright (C) 2008 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"...
(gdb) r
Starting program: /tmp/a.out
elfread.c:424: 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)

> The other thing that may help figuring out the problem is to run gdb
> under itself:
>
> gdb -ex 'set prompt (top) ' --args gdb /path/to/app
> (top) break internal_error
> # Should set breakpoint 1 in the inferior GDB
> (top) run
> (gdb) run
> # Should stop at breakpoint 1
> (top) where full
>
Breakpoint 1, 0x000738d8 in internal_error ()
(top) where full
#0  0x000738d8 in internal_error ()
No symbol table info available.
#1  0x00128cf4 in ?? ()
No symbol table info available.
#2  0x00128cf4 in ?? ()
No symbol table info available.
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Would it help if I rebuilt gdb with symbols and reran this test, or maybe
it should be submitted as a bug to the Solaris maintainers? It is quite
conceivable that upgrading from snv103 to snv112 might fix this problem,
so does anyone at gdb want to work on this before I do so?