Can anyone help with a problem I'm having getting GDB talking to a remote target. I'm trying to get GDB working with an application running on a proprietary board with a Motorola MPC755. The comms is through shared memory, so I have written a TCP/IP socket to shared memory comms program, and use the 'target remote <host>:<port>' command in GDB to start things off.
I have taken the ppc-stub file and modified it to work with our application, and I start to get GDB talking the to remote program, but when it asks for the registers ($g#67) and we send back the contents, GDB reports - Couldn't establish connection to remote target procfs: couldn't find pid 42000 in procinfo list. I am running GDB under Solaris 2.8. Do I need to build gdb for the power-pc target or does it automatically determine the target type ? Is there any more documentation on remote debugging other than the GDB manual at gnu.org ? I'm pretty sure the comms are ok because I'm dumping the data following through the socket and I see the following: from socket data[9]='+$Hc-1#09' from card data[7]='+$OK#9a' from socket data[7]='+$qC#b4' from card data[5]='+$#00' from socket data[13]='+$qOffsets#4b' from card data[5]='+$#00' from socket data[6]='+$?#3f' from card data[8]='+$S05#b8' from socket data[8]='+$Hg0#df' from card data[7]='+$OK#9a' from socket data[6]='+$g#67' from card data[1]='+' from card data[260]='$fff0cbdcffffffa8fff0f0b8fff1a0d8fff1a51000009070000000000000000700000007ffffff58fffffe58ffffffa800010000fff1a49000000000000000000000000000000000000000000000000000000000fff141b0fff141b0fff10000fff10000ffffff98ffffffa8ffffffb0fff10000fff1448cfff14488ffffffe0#04' from socket data[1]='+' other end closed the client has disconnected The regsiter contents is this example are shorter than the full list in ppc-stub.c, as I thought there might have been too much data. Any help or pointers would be great. Thanks, Murray. _______________________________________________ Bug-gdb mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-gdb