I had several replies, each of which told me that they also found
that gdb does not work under 5.1a.
One person did refer me to the following section extracted from
a gdb README file:
alpha-dec-osf5.1
GDB 5.1 has a number of problems on this platform (Ref PR gdb/237). A
GDB 5.1 built with ``CC="cc -DUSE_LDR_ROUTINES"'' is reported to work
much better.
I tried this, but gdb still failed with exactly the same error.
In summary, there was no solution, except to wait for a new release
of gdb.
Here's my original posting:
On Wed, 9 Jan 2002, Richard Fairfield wrote:
>
> Hello All:
>
> I recently compiled and installed gcc 3.0 on our Alphas running
> Tru64 UNIX 5.1a. I then used that version of gcc to build gdb 5.1.
> The compilation of both gcc and gdb was done one an Alpha 600 5/333
> (an EV5 machine).
>
> Gdb 5.1 compiled without errors, but fails when I try to use it.
> For example, I start with this tiny "hello world" program:
>
> #include <stdio.h>
> main(int argc,char *argv[]) {
> printf("Hello World\n");
> }
>
> I compile it like this:
>
> gcc -g hello_world.c
>
> The program runs correctly:
>
> % ./a.out
> Hello World
>
> I then run gdb like this:
>
> gdb a.out
>
> Here's the resulting gdb output, showing the errors:
>
> *******************
> GNU gdb 5.1
> Copyright 2001 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 "alphaev5-dec-osf5.1"...mdebugread.c:2448: gdb-intern
> al-error: Section index is uninitialized
>
> An internal GDB error was detected. This may make further
> debugging unreliable. Continue this debugging session? (y or n) y
>
> Create a core file containing the current state of GDB? (y or n) n
>
> (gdb) run
> Starting program: /user0/rcf/src/test/c-test/a.out
> Illegal instruction (core dumped)
> *******************
>
>
> Has anyone else seen this problem? Any solutions?
>
> Thank you,
> Richard Fairfield
> Math Sciences Computing Center
> University of Washington
> MSCC Departmental Telephone Number: 206-616-3636
> My Office Telephone Number: 206-685-2303
> Fax: 206-685-7419
> rcf_at_ms.washington.edu
>
>
Received on Fri Jan 11 2002 - 05:01:14 NZDT