From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from conssluserg-03.nifty.com (conssluserg-03.nifty.com [210.131.2.82]) by sourceware.org (Postfix) with ESMTPS id 6BB373857C50 for ; Thu, 11 Nov 2021 12:03:02 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 6BB373857C50 Authentication-Results: sourceware.org; dmarc=fail (p=none dis=none) header.from=nifty.ne.jp Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=nifty.ne.jp Received: from Express5800-S70 (z221123.dynamic.ppp.asahi-net.or.jp [110.4.221.123]) (authenticated) by conssluserg-03.nifty.com with ESMTP id 1ABC2X3p031971 for ; Thu, 11 Nov 2021 21:02:33 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-03.nifty.com 1ABC2X3p031971 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.ne.jp; s=dec2015msa; t=1636632153; bh=LFRlXaGpg+7WbntLbDdi41UTDuJWLK19M2iU5IE+R6Y=; h=Date:From:To:Subject:In-Reply-To:References:From; b=KFLou/XVIiCCCq/1kfqltuOmEzrLNtDuwfBjGZjbbTCd0kBIZr4afUnXowjwWPXtI MQYabM0UbD1RpdSF/nPF11Q5OkIjRAvVZM19xgRUz4CrixmY2yThpcE41Ru5fWwOeH vGuPsiiUZO00327Z+j4QyUI0+5tAUeHKq6So0jw1nTpcsWxnhMEyBw6JBUkIOKbCb2 5nbD1B4C1CsKYbWUqW2vAbxtZBY7G4lNhogucKumUDhvHBw8rKIu528rJ0CGHrwVyg P4OljWa07neXZtR/r5APJ/bueI2PtVZlQmYrkgFCcC0WSgF82rjPT/36at2Jj4wVz1 MFQeYpS47RfBQ== X-Nifty-SrcIP: [110.4.221.123] Date: Thu, 11 Nov 2021 21:02:34 +0900 From: Takashi Yano To: cygwin-developers@cygwin.com Subject: Re: 3.3.0: Possible regression in cygwin DLL (Win10); fixed in snapshot Message-Id: <20211111210234.6a43a2ba237cef11ecc7016b@nifty.ne.jp> In-Reply-To: References: <20211106044116.698b465a5d8ed6ce2cc75c99@nifty.ne.jp> <2cfa5de7-3b95-9062-4572-f36d304bc916@cornell.edu> <20211106151047.4d8f626bd6ebe9e4d8017f3b@nifty.ne.jp> <20211110173003.88359e8482ffa8b8be326903@nifty.ne.jp> <20211110223049.b61c6cb87fb3e540b4214bcf@nifty.ne.jp> <20211111201206.72cd688ce6a0d72d3a4f6c5f@nifty.ne.jp> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.2 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin-developers@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin core component developers mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Nov 2021 12:03:04 -0000 On Thu, 11 Nov 2021 12:33:21 +0100 Corinna Vinschen wrote: > On Nov 11 20:12, Takashi Yano wrote: > > > [FileProcessIdsUsingFileInformation] > > > > Thanks for advice. get_query_hdl_per_* is called in the write side, > > so only knows pipe handle of the write side. We would like to know > > ProcessId which have pipe handle of the read side. Can we use > > FileProcessIdsUsingFileInformation for this perpose? > > I don't know. I just stumbled over it yesterday and I thought it might > be something we could utilize. Supposedly it returns PIDs for processes > having that file open, but how this works for pipe read/write sides > needs testing. Of course, knowing how Windows functions usually only go > half the way, the function will either only return the current side of > the pipe, or even an error code :-/ Never mind, it was just an idea. I have tested the behaviour of FileProcessIdsUsingFileInformation just now. We can use it! I will try to use it in get_query_hdl(). Thanks! -- Takashi Yano