This is the mail archive of the
gdb@sourceware.cygnus.com
mailing list for the GDB project.
Re: gdbserver exiting
- To: Stan Shebs <shebs AT cygnus dot com>
- Subject: Re: gdbserver exiting
- From: Kevin Hilman <khilman AT equator dot com>
- Date: 16 Sep 1999 09:47:24 -0700
- Cc: gdb AT sourceware.cygnus dot com
- Organization: None to speak of.
- References: <199909152031.NAA05727@andros.cygnus.com>
- Reply-To: Kevin Hilman <khilman AT equator dot com>
Stan Shebs <shebs@cygnus.com> writes:
> From: Kevin Hilman <khilman@equator.com>
> Date: 15 Sep 1999 13:14:58 -0700
>
> I working on a port of gdbserver. I'd like to convince gdbserver to
> exit when gdb exits since it's a multi-user environment and each user
> will run their own instance of gdbserver. Is there anything part
> of the protocol to do this, or should I add my own extention to
> the protocol.
>
> Yes, the existing "k" packet should do what you want. If GDB has a
> live connection via "target remote", and you quit, it will send a
> "k" packet. In fact, my version of gdbserver exits when it receives
> a "k", unless you're using extended-remote, what version are you
> using? From gdbserver/server.c:
This was my stupidity here. I was getting the 'k' packet, but
my kill_inferior() wasn't doing the right thing.
Thanks!
-kev-