From: Andrew Cagney <ac131313@cygnus.com>
To: Michael Snyder <msnyder@cygnus.com>
Cc: gdb-patches@sources.redhat.com, cagney@redhat.com
Subject: Re: [RFC] remote: semantics of 'k' (kill) message
Date: Sun, 03 Feb 2002 18:32:00 -0000 [thread overview]
Message-ID: <3C5DF2A2.2010601@cygnus.com> (raw)
In-Reply-To: <200202011729.g11HTY301250@reddwarf.cygnus.com>
> Andrew, you recently added this comment:
>
> ! FIXME: @emph{There is no description of how to operate when a specific
> ! thread context has been selected (ie.@: does 'k' kill only that thread?)}.
>
> Maybe with a little discussion we can resolve this?
> I believe the 'k' message is only sent in one context:
> when the user asks gdb to kill the inferior process.
> On a native system, that is clearly interpreted as meaning
> to kill all of the threads. Is there any reason why we
> should not agree that it means the same thing on an
> embedded target?
Hmm, yes. You're right. I shouldn't be trying to specify ``future
behavour'' in the protocol. Rather it should just be specifying things
based on GDB's existing behavour on a well implemented native system.
Andrew
next prev parent reply other threads:[~2002-02-04 2:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 9:36 Michael Snyder
2002-02-03 18:32 ` Andrew Cagney [this message]
2002-02-03 22:59 ` Michael Snyder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C5DF2A2.2010601@cygnus.com \
--to=ac131313@cygnus.com \
--cc=cagney@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox