I have a couple of questions about gdb debugging on the simulator.
I am running the cell simulator (sdk 2.1) on an x86 system, Nad I followed the instructions written on the web page:
I used the first script in that page to install the 64-bit power pc version of gdb; I recompiled the 'simple' example i the tutorial of sdk with CFLAGS = -g; configured bogusne (the host system and the simulator can ping each other).
now, I launch on the simulator gdbserver (with the command: ppu-gdbserver :1000 ./simple) and launch on the host system the gdb program (with the command: powerpc64-linux-gdbtui simple).
The gdbserver correctly starts listening, giving me the output:
Process ./simple created; pid = 430
Listening on port 1000
on the host system, the gdb whows me the source code and its command propmpt.
but when I type, in the gdb console, the command: target remote 172.20.0.2:1000
I obtain the output:
REmote debugging using 172.20.0.2:1000
Couldn't establish connection to remote target
Roemte registry badly formatted: T0501:00000000fd00fbd0;40:00000000f7fe6660;
I tried to google te solution, but I really can't figure out where can be the problem... any help??
The second question is: as explained in the page previously linked, I'd like to "debug cell BE applications": I'd like to start the execution of a ppu program, and then attach gdb to the sou program when created by the ppu program.
The page suggests to set an enviroment variable, but once again, if I type:
- SPU_DEBUG_START=1 ./my_program &
The execution of the program doesn't stops at spu thread creation, as I'd expect. The program executes without any stop, reaching the end of the execution.
Again, where can be the problem? Am I missing to do something??
Thanks in advance for your help.