From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id +DN9Hy8WHWLFVAAAWB0awg (envelope-from ) for ; Mon, 28 Feb 2022 13:36:31 -0500 Received: by simark.ca (Postfix, from userid 112) id 7DD8D1F3CB; Mon, 28 Feb 2022 13:36:31 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-3.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,NICE_REPLY_A,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 2FBA21F3B5 for ; Mon, 28 Feb 2022 13:36:22 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id B1083385841C for ; Mon, 28 Feb 2022 18:36:21 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B1083385841C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1646073381; bh=Wtazb3xpupfhlQDCSxqBRyPXB294AP/2aNrBVGNGaTw=; h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=h2iy2rhvLfDPzWepqpCeXdb3XXcBB+VpgjpQU25eWp0WrN1EKI9xkN3hj17IGDs6l Qv0BdQkMIHCf1gF5gpisX36FEhoSCrsHj4pZhFXHprDkSKrdBslQxWwYMbqafMYMAZ hrch6seJThaZpScT4CTZT+cO3yy37Nt4vGwDkFUo= Received: from smtp.polymtl.ca (smtp.polymtl.ca [132.207.4.11]) by sourceware.org (Postfix) with ESMTPS id 69023385842A for ; Mon, 28 Feb 2022 18:34:41 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 69023385842A Received: from simark.ca (simark.ca [158.69.221.121]) (authenticated bits=0) by smtp.polymtl.ca (8.14.7/8.14.7) with ESMTP id 21SIYOP1010214 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 28 Feb 2022 13:34:29 -0500 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.polymtl.ca 21SIYOP1010214 Received: from [10.0.0.11] (192-222-157-6.qc.cable.ebox.net [192.222.157.6]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id 1D70D1EDF0; Mon, 28 Feb 2022 13:34:24 -0500 (EST) Message-ID: <76ee0fd0-d42f-e811-bd96-1766e2514191@polymtl.ca> Date: Mon, 28 Feb 2022 13:34:23 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1 Subject: Re: [RFC][PATCH v3 1/1][PR gdb/24069] gdb/darwin: skip over WIFSTOPPED wait4 status Content-Language: en-US To: Philippe Blain , gdb-patches@sourceware.org References: <20220216141540.96514-1-levraiphilippeblain@gmail.com> <20220224142321.585-1-levraiphilippeblain@gmail.com> <20220224142321.585-2-levraiphilippeblain@gmail.com> <50083fbd-bb00-da50-26a6-0bc5c6dcc34d@polymtl.ca> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Poly-FromMTA: (simark.ca [158.69.221.121]) at Mon, 28 Feb 2022 18:34:24 +0000 X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Simon Marchi via Gdb-patches Reply-To: Simon Marchi Cc: Louis-He <1726110778@qq.com>, Dominique Quatravaux , Sam Warner Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" On 2022-02-28 12:52, Philippe Blain wrote: > Hi Simon, > > Le 2022-02-24 à 10:49, Simon Marchi a écrit : >> >> >> On 2022-02-24 09:23, Philippe Blain wrote: >>> From: Dominique Quatravaux >>>> >>> >>> PR gdb/24609 >>> * gdb/darwin-nat.c (darwin_nat_target::decode_message): Also >>> check for WIFSTOPPED upon MACH_NOTIFY_DEAD_NAME. >> >> Thanks, pushed. >> >> Simon >> > > I noticed that the Bugzilla entry was not updated when you pushed > that commit, whereas it was for the previous one [1]. I'm not sure > of what is the automation that makes this work... > > I thought it was because my changelog entry mistakenly used 24609 instead > of 24069, but that was the case also for v2 1/2, so I guess that's not > the cause... Patch #1 had a link to the correct bugzilla ticket in its commit message, so the connection was made. Patch #2 didn't have any mention of the bugzilla ticket, so there was no connection. The correct thing to do nowadays, according to our standard procedures, would have been to use the: Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=24069 trailer. But I often forget about it. Simon