From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4101 invoked by alias); 14 Nov 2014 17:33:01 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 4088 invoked by uid 89); 14 Nov 2014 17:33:00 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Fri, 14 Nov 2014 17:32:59 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 0889B116ACD; Fri, 14 Nov 2014 12:32:58 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id X6vc8RZgGVAh; Fri, 14 Nov 2014 12:32:57 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 98AA41166E4; Fri, 14 Nov 2014 12:32:57 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 045E440F79; Fri, 14 Nov 2014 21:32:56 +0400 (RET) Date: Fri, 14 Nov 2014 17:33:00 -0000 From: Joel Brobecker To: Pedro Alves Cc: gdb-patches@sourceware.org Subject: Re: [RFA/Linux] Ask kernel to kill inferior when GDB terminates Message-ID: <20141114173255.GD5774@adacore.com> References: <1415984034-27122-1-git-send-email-brobecker@adacore.com> <54663729.6010708@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54663729.6010708@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-SW-Source: 2014-11/txt/msg00330.txt.bz2 > I could see this making some sense when GDB has spawned the process, > but it seems harsh when GDB has attached to the process instead > of spawning it? Hmmm, good point. I'd like to verify what happens in that case, and whether the process remains stopped or if execution resumes in that case. > Note that Windows has had a similar feature for > ages (DebugSetProcessKillOnExit), and how windows-nat.c calls > DebugSetProcessKillOnExit(false) when GDB attaches to a process. Thanks, Pedro. -- Joel