So, the GDB manual has this to say about remote debugging:

     To resume the remote program and stop debugging it, use the `detach'
  command.

This is not how gdbserver works, and it isn't how any stubs I've worked with
behave, either.  They'll sit and wait for a reconnection.  Rather than
change the status quo, I would like to update the documentation and provide
a way to get the previously documented behavior.  This uses the "K" packet
described in my email to gdb@ last week.  The new command is `detach remote'
which I'm not thrilled with but I'm a little short on ideas.  It's hard to
find something to call this.

GDB and gdbserver patches attached.  Comments?


-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer