From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11080 invoked by alias); 25 Nov 2005 18:35:09 -0000 Received: (qmail 11073 invoked by uid 22791); 25 Nov 2005 18:35:08 -0000 X-Spam-Check-By: sourceware.org Received: from fra-del-01.spheriq.net (HELO fra-del-01.spheriq.net) (195.46.51.97) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 25 Nov 2005 18:35:07 +0000 Received: from fra-out-02.spheriq.net (fra-out-02.spheriq.net [195.46.51.130]) by fra-del-01.spheriq.net with ESMTP id jAPIZ33o004767 for ; Fri, 25 Nov 2005 18:35:03 GMT Received: from fra-cus-02.spheriq.net (fra-cus-02.spheriq.net [195.46.51.38]) by fra-out-02.spheriq.net with ESMTP id jAPIZ2Ii026809 for ; Fri, 25 Nov 2005 18:35:03 GMT Received: from beta.dmz-eu.st.com (beta.dmz-eu.st.com [164.129.1.35]) by fra-cus-02.spheriq.net with ESMTP id jAPIYrXh007990 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Fri, 25 Nov 2005 18:34:54 GMT Received: from zeta.dmz-eu.st.com (ns2.st.com [164.129.230.9]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id E3FD6DA45; Fri, 25 Nov 2005 18:34:53 +0000 (GMT) Received: by zeta.dmz-eu.st.com (STMicroelectronics, from userid 60012) id 8B0FF4751F; Fri, 25 Nov 2005 18:37:56 +0000 (GMT) Received: from zeta.dmz-eu.st.com (localhost [127.0.0.1]) by zeta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 511EF75995; Fri, 25 Nov 2005 18:37:56 +0000 (UTC) Received: from mail1.bri.st.com (mail1.bri.st.com [164.129.8.218]) by zeta.dmz-eu.st.com (STMicroelectronics) with ESMTP id DFCEC4748C; Fri, 25 Nov 2005 18:37:55 +0000 (GMT) Received: from [164.129.15.13] (terrorhawk.bri.st.com [164.129.15.13]) by mail1.bri.st.com (MOS 3.5.8-GR) with ESMTP id CHA04933 (AUTH "andrew stubbs"); Fri, 25 Nov 2005 18:34:51 GMT Message-ID: <4387589C.6070305@st.com> Date: Fri, 25 Nov 2005 20:13:00 -0000 From: Andrew STUBBS User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) MIME-Version: 1.0 To: Daniel Jacobowitz Cc: gdb-patches@sources.redhat.com Subject: Re: [PATCH] SIGTERM handler References: <437B6374.1@st.com> <20051125175433.GA736@nevyn.them.org> In-Reply-To: <20051125175433.GA736@nevyn.them.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-O-Spoofed: Not Scanned X-O-General-Status: No X-O-Spam1-Status: Not Scanned X-O-Spam2-Status: Not Scanned X-O-URL-Status: Not Scanned X-O-Virus1-Status: No X-O-Virus2-Status: Not Scanned X-O-Virus3-Status: No X-O-Virus4-Status: No X-O-Virus5-Status: Not Scanned X-O-Image-Status: Not Scanned X-O-Attach-Status: Not Scanned X-SpheriQ-Ver: 4.2.0 X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2005-11/txt/msg00467.txt.bz2 Daniel Jacobowitz wrote: > I'm dubious as to the value of this, but why not - patch is OK. I > never send GDB a SIGTERM, but I send it SIGKILL on a regular basis. > I guess it may get SIGTERMs during clean shutdown. Thanks, committed. FYI, this is critical here because we use the debugger with an alternative simulator (somewhat more accurate than the ISS in GDB). If GDB does not shut down cleanly then the simulator does not shut down cleanly. This might be bad enough, but sometimes it will happily go on simulating an infinite loop and consume all the host CPU. This is particularly unhelpful when run as part of a long test and the SIGTERM is the result of a timeout. It also ensures --return-child-result is good, resets connections to remote targets and probably helps out many other issues. Andrew