When debugging with gdbserver/gdb the debugger loses control=20
of the threads. I did set the sysroot variable right, and I=20
don't get the ld not found error message.
Basically, I cannot step into pthread_create, without losing=20
control, with the software not running and gdb going timeout.=20
Sometimes the gdbserver shell prints out "ptrace(): pid not=20
found", or I get E01 reply on the gdb-cross. Putting=20
breakpoints into threads works sometimes.
My ultimate goal would be to make it work with Eclipse, but=20
it's a long way from having it working with such a system.
Try to change the way GDB handle some of the signals, I don't recall
which signal in this respect though. You can do this using the 'handle'
command.