From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 33009 invoked by alias); 25 Jan 2018 22:39:18 -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 33000 invoked by uid 89); 25 Jan 2018 22:39:18 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy= X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 25 Jan 2018 22:39:17 +0000 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 46689883C6 for ; Thu, 25 Jan 2018 22:39:16 +0000 (UTC) Received: from [127.0.0.1] (ovpn04.gateway.prod.ext.ams2.redhat.com [10.39.146.4]) by smtp.corp.redhat.com (Postfix) with ESMTP id E51B260BF2; Thu, 25 Jan 2018 22:39:10 +0000 (UTC) Subject: Re: [PATCH] Always print "Detaching after fork from child..." To: Sergio Durigan Junior References: <20180124194714.26222-1-sergiodj@redhat.com> <20180124204339.GA16117@host1.jankratochvil.net> <87mv13x9g1.fsf@redhat.com> <93ffe8e4-ad56-01b1-c0b5-f9d9c5fb71ec@redhat.com> <87lgglwuzc.fsf@redhat.com> Cc: Jan Kratochvil , GDB Patches From: Pedro Alves Message-ID: Date: Thu, 25 Jan 2018 22:39:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <87lgglwuzc.fsf@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2018-01/txt/msg00543.txt.bz2 On 01/25/2018 08:20 PM, Sergio Durigan Junior wrote: > On Thursday, January 25 2018, Pedro Alves wrote: >> But we can fix that, I think. See a quick straw-man patch below. >> (Really just a a straw-man; there's more redundancy if you do "follow-fork child", >> for example.) > > Thanks for the reply and the patch. It is my understanding that you > would like it to be extended in order to avoid redundancy in other > cases. I will take a look at it. Yes, if this is the direction to go then we'll need to make sure that the output of both "set print inferior-events off/on" looks reasonable in the multiple use cases that spawn / attach / fork / detach / kill etc. inferiors, with both native and remote debugging. Thanks, Pedro Alves