From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 23 Jan 2002 17:16:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 23 Jan 2002 17:16:08 -0500 Received: from mail.parknet.co.jp ([210.134.213.6]:17162 "EHLO mail.parknet.co.jp") by vger.kernel.org with ESMTP id ; Wed, 23 Jan 2002 17:15:49 -0500 To: vic Cc: Mike Coleman , marcelo@conectiva.com.br, linux-kernel@vger.kernel.org, torvalds@transmeta.com, alan@lxorguk.ukuu.org.uk Subject: Re: [PATCH] ptrace on stopped processes (2.4) In-Reply-To: <87g0632lzw.fsf@mathdogs.com> <878zawvl1v.fsf@devron.myhome.or.jp> From: OGAWA Hirofumi Date: Thu, 24 Jan 2002 07:14:17 +0900 In-Reply-To: Message-ID: <87r8ogr9za.fsf@devron.myhome.or.jp> User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org vic writes: > Now I see the problem with PTRACE_KILL. Thanks for the example. > > I'm looking into it. I need to justify the quoted portion of the > patch or find a better way to get its effect. > > In the meantime, the problem could be fixed by changing the > PTRACE_KILL implementation to call send_sig instead of setting > exit_code. How does that strike people? PTRACE_SYSCALL, PTRACE_CONT, and PTRACE_SINGLESTEP can't send a signal by the same reason. Please read the do_signal(). -- OGAWA Hirofumi