Re: [RFC] gdb.server testcases (resend)

[Manoj Iyer <manjo@austin.ibm.com>]

Looks like RHEL 4 ships wrong kernel headers, on RHEL4
/usr/include/linux/version.h: #define UTS_RELEASE "2.4.20", your patch
works sorta on SLES (/usr/include/linux/version.h: #define
UTS_RELEASE "2.6.5") running on a power5.

On the host side
----------------
 ./gdbserver 9.3.190.182:1234 /tmp/test
Process /tmp/test created; pid = 8323
Stop pc is 0x40010470
Listening on port 1234
Remote debugging from host 9.3.190.187
readchar: Got EOF
Remote side has terminated connection.  GDBserver will reopen the
connection.
Listening on port 1234


On remote side
--------------
 ./gdb
GNU gdb 6.3.50.20050516-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".
Setting up the environment for debugging gdb.
No symbol table is loaded.  Use the "file" command.
No symbol table is loaded.  Use the "file" command.
.gdbinit:8: Error in sourced command file:
No breakpoint number 0.
(gdb) file /tmp/test
Reading symbols from /tmp/test...done.
Using host libthread_db library "/lib64/tls/libthread_db.so.1".
(gdb) target remote 9.3.190.182:1234
Remote debugging using 9.3.190.182:1234
Remote register badly formatted:
T0501:00000000ffffe6b0;40:0000000040010470;
here: fffe6b0;40:0000000040010470;
(gdb)

-----
manjo
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Cogito ergo sum                                                          +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

On Wed, 18 May 2005, Daniel Jacobowitz wrote:

> On Wed, May 18, 2005 at 10:37:56AM -0500, Manoj Iyer wrote:
> >
> > Daniel,
> >
> > The patches did not apply cleanly to mainline, so I had to hand patch the
> > files. Also, in the final link stage for gdbserver ld complained that:
> >
> > /usr/bin/ld: warning: powerpc:common64 architecture of input file
> > `inferiors.o' is incompatible with powerpc:common output
> >
> > so I had to add a -m64 to the linker call.
> >
> > gdbserver still broken:.
> >
> > $ ./gdbserver uranus.ltc.austin.ibm.com /tmp/server
> > Process /tmp/server created; pid = 4747
> > reading register 70: Input/output error
> > Exiting
>
> My reading of the kernel source suggests that FPSCR should be accessible
> using that address.  You should figure out why it isn't.
>
> At a guess your headers are broken:
>       /* NOTE: cagney/2005-02-08: On some 64-bit GNU/Linux systems the
>          kernel headers incorrectly contained the 32-bit definition of
>          PT_FPSCR.  For the 32-bit definition, floating-point
>          registers occupy two 32-bit "slots", and the FPSCR lives in
>          the secondhalf of such a slot-pair (hence +1).  For 64-bit,
>          the FPSCR instead occupies the full 64-bit 2-word-slot and
>          hence no adjustment is necessary.  Hack around this.  */
>
> --
> Daniel Jacobowitz
> CodeSourcery, LLC
>