when I compile GDB (mainline CVS) with the GCC 3.4 compiler I get the
following problem. But with gcc version 3.3.3 (SuSE Linux) it does not
happen. I have attached the testcase. To recreate the bug.
- cc -m64 -o tbug64 tbug.c -lpthread
- src/gdb/gdb tbug64
- (gdb) run

Anyone seen this problems before? any known solutions?


Kernel: 2.6.7-1.451.2.3
OS: Redhat
GCC: gcc version 3.4.1 20040702 (Red Hat Linux 3.4.1-2)

[root@ppc64hlp3 src]# ./gdb/gdb /tmp/gdb64
GNU gdb 2004-08-27-cvs
Copyright 2004 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 "powerpc64-unknown-linux-gnu".../tmp/gdb64: No
such file or directory.

(gdb) run
Starting program:
No executable file specified.
Use the "file" or "exec-file" command.
(gdb) file /tmp/tbug64
Reading symbols from /tmp/tbug64...done.
Using host libthread_db library "/lib64/tls/libthread_db.so.1".
(gdb) run
Starting program: /tmp/tbug64
[Thread debugging using libthread_db enabled]
Error while reading shared library symbols:
reading register fpscr (#70): Input/output error.
Killed
[root@ppc64hlp3 src]#


Any thoughts?

Thanks
-----
manjo
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Cognito ergo sum                                                          +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++