This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFC] gdb.server testcases (resend)
- From: Daniel Jacobowitz <drow at false dot org>
- To: Wu Zhou <woodzltc at cn dot ibm dot com>
- Cc: Manoj Iyer <manjo at austin dot ibm dot com>, gdb-patches at sources dot redhat dot com
- Date: Sun, 22 May 2005 13:15:20 -0400
- Subject: Re: [RFC] gdb.server testcases (resend)
- References: <1116490026.428c492a8f3d8@imap.linux.ibm.com>
On Thu, May 19, 2005 at 04:07:06AM -0400, Wu Zhou wrote:
> 2. 64-bits gdbserver with 32-bits debuggee
>
> without Daniel's patch, the 64-bits gdbserver on my power4 box also
> report "reading register I/O error" at register 1. After applying
> Daniel's patch, gdbserver could start the 32-bits debuggee and begin
> to wait for the remote gdb's connection.
>
> On the host side, my gdb session is somewhat the same as yours. It
> seems that gdb at the host side expects 32-bits register, something
> like:
>
> T0501:ffffe6b0;40:40010470;
>
> but the remote gdbserver sends back 64-bits value:
>
> T0501:00000000ffffe6b0;40:0000000040010470;
>
> So it report "Remote register badly formatted" error.
Yes, this will not work. The correct way to handle this is to wait
until I have implemented the available target features proposal I've
posted on gdb@, and then I can make gdbserver inform GDB that 64-bit
registers are available so that it will expect them.
This will require some surgery in GDB, I'm sure. The way MIPS
implements this is not very reliable.
> Program received signal SIGFPE, Arithmetic exception.
> 0x000000800013fd64 in .vfprintf () from /lib64/tls/libc.so.6
> (gdb)
>
I have no idea what causes this one, sorry.
--
Daniel Jacobowitz
CodeSourcery, LLC