From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30909 invoked by alias); 4 Feb 2002 06:59:18 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 30747 invoked from network); 4 Feb 2002 06:59:14 -0000 Received: from unknown (HELO cygnus.com) (205.180.230.5) by sources.redhat.com with SMTP; 4 Feb 2002 06:59:14 -0000 Received: from telocity.telocity.com (taarna.sfbay.redhat.com [205.180.230.102]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with SMTP id WAA06621; Sun, 3 Feb 2002 22:59:11 -0800 (PST) Message-ID: <3C5E3030.5E6B@redhat.com> Date: Sun, 03 Feb 2002 22:59:00 -0000 From: Michael Snyder X-Mailer: Mozilla 3.04 (Win95; I) MIME-Version: 1.0 To: Andrew Cagney CC: Michael Snyder , gdb-patches@sources.redhat.com, cagney@redhat.com Subject: Re: [RFC] remote: semantics of 'k' (kill) message References: <200202011729.g11HTY301250@reddwarf.cygnus.com> <3C5DF2A2.2010601@cygnus.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-02/txt/msg00063.txt.bz2 Andrew Cagney wrote: > > > 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. Well, we might conceivably want to be able to kill a specified thread or process on an embedded system -- but at present we can't do that on a native system either.