gdbserver (arm,natty) <-> gdb (ia32,natty) fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gdb (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gdb
Attempting a remote debug session.
On the arm machine:
tgall@halimede:~$ gdbserver 192.168.1.15:1234 /bin/ls
Process /bin/ls created; pid = 15437
Listening on port 1234
Remote debugging from host 192.168.1.15
readchar: Got EOF
Remote side has terminated connection. GDBserver will reopen the connection.
Listening on port 1234
On the intel machine using gdb-mutliarch
gdb-multiarch /bin/ls
GNU gdb (Ubuntu/Linaro 7.2-1ubuntu10) 7.2
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://
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 "i686-linux-gnu".
For bug reporting instructions, please see:
<http://
Reading symbols from /bin/ls...(no debugging symbols found)...done.
(gdb) target remote 192.168.1.14:1234
Remote debugging using 192.168.1.14:1234
warning: Architecture rejected target-supplied description
Remote 'g' packet reply is too long: 000000002959b2b
(gdb)
Version info:
ia32: gdb-multiarch 7.2-1ubuntu10
armel: gdbserver 7.2-1ubuntu10
Arm box
root@halimede:~# lsb_release -rd
Description: Ubuntu Natty (development branch)
Release: 11.04
intel box
tgall@proteus:~$ lsb_release -rd
Description: Ubuntu Natty (development branch)
Release: 11.04
When you say:
"On the intel machine using gdb-mutliarch
gdb-multiarch /bin/ls"
are you actually refering to the Intel copy of /bin/ls ?
This will cause GDB to expect to debug Intel architecture, which does not agree with an ARM architecture being reported by the remote stub.
You should use a copy of the *ARM* binary on the Intel machine when starting GDB ...