From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22487 invoked by alias); 21 Sep 2010 23:54:04 -0000 Mailing-List: contact archer-help@sourceware.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Received: (qmail 22476 invoked by uid 22791); 21 Sep 2010 23:54:04 -0000 X-SWARE-Spam-Status: No, hits=-4.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Roland McGrath To: Oleg Nesterov X-Fcc: ~/Mail/utrace Cc: archer@sourceware.org Subject: Re: [BUG] gdb: quit hangs after step into signal handler In-Reply-To: Oleg Nesterov's message of Monday, 20 September 2010 23:17:15 +0200 <20100920211715.GA10574@redhat.com> References: <20100920211715.GA10574@redhat.com> Message-Id: <20100921235356.BB1F340614@magilla.sf.frob.com> Date: Tue, 21 Sep 2010 23:54:00 -0000 X-SW-Source: 2010-q3/txt/msg00209.txt.bz2 > Probably gdb should just do kill(tracee, SIGKILL) when it wants > to terminate the tracee. That's what I recommend. (You only need one SIGKILL per process, not one for each thread. But if you still support linuxthreads, that will probably need one for each thread.) Even if you were paranoid about some old kernel where PTRACE_KILL might work better (dubious if there are any such, but that's why it's paranoia), you could do this before PTRACE_KILL and it should certainly be fine everywhere. Thanks, Roland