From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 67515 invoked by alias); 14 Apr 2016 16:41:22 -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 67502 invoked by uid 89); 14 Apr 2016 16:41:21 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy= X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Thu, 14 Apr 2016 16:41:11 +0000 Received: from svr-orw-fem-02x.mgc.mentorg.com ([147.34.96.206] helo=SVR-ORW-FEM-02.mgc.mentorg.com) by relay1.mentorg.com with esmtp id 1aqkKL-00000a-2p from Luis_Gustavo@mentor.com ; Thu, 14 Apr 2016 09:41:09 -0700 Received: from [172.30.5.188] (147.34.91.1) by svr-orw-fem-02.mgc.mentorg.com (147.34.96.168) with Microsoft SMTP Server id 14.3.224.2; Thu, 14 Apr 2016 09:41:08 -0700 Subject: Re: ping: [PATCH 1/3] Never kill PID on: gdb exec PID References: <20160414154439.GA1489@host1.jankratochvil.net> To: Jan Kratochvil , Reply-To: Luis Machado From: Luis Machado Message-ID: <570FC823.7020908@codesourcery.com> Date: Thu, 14 Apr 2016 16:41:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <20160414154439.GA1489@host1.jankratochvil.net> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2016-04/txt/msg00336.txt.bz2 On 04/14/2016 10:44 AM, Jan Kratochvil wrote: > It would be nice to upstream at least this fix of the series: > Subject: [PATCH 1/3] Never kill PID on: gdb exec PID > Message-ID: <20151016204733.27288.56498.stgit@host1.jankratochvil.net> > https://sourceware.org/ml/gdb-patches/2015-10/msg00301.html > Is this still happening after 57d1de9cf3ba8dd98eaf4a3d131c05ec4c49779d? I couldn't reproduce what you saw with master GDB.