if you use gdbserver to listen on a port and the specified program fails to 
launch properly, the server process will continue on to the accept() call and 
sit there forever ... you cant control+c the process as the signals are taken 
over which means you have to connect with gdb to force the server to re-check 
itself and then abort ... all in all, a pita for a simple typo.

the attached patch checks the status field immediately after launch rather 
than falling down into the main loop and waiting for the remote debugger to 
connect for the status to get properly checked.
-mike