X-Recipient: archive-cygwin@delorie.com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C7D013858C41
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1693230446;
	bh=zINJ/W4+E3LVq2cVcpyuwpk64rvxMyKp0hqv/yyHHFw=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	 From;
	b=VrNUtTQByGCAci+/09fz6mNkPTifRyJgP//9CY/wo3vHIGHLimS4PUJJ0oqoitxI7
	 T4kwyk9lIA6alAq1rZvqGRf5fJBGLbpkbhu36ooZ05k8KNBeFhFDfwV+HgZv6zfrkm
	 a8xZfllPWk4gtLj68baOOZ97j/bgXQB60Y33x0+4=
X-Original-To: cygwin@cygwin.com
Delivered-To: cygwin@cygwin.com
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org AB7E9385841C
Date: Mon, 28 Aug 2023 22:46:51 +0900
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: [EXTERNAL] Re: scp stalls on uploading in cygwin 3.5 current
 master.
Message-Id: <20230828224651.c16b295ad5cf10381a5fa47d@nifty.ne.jp>
In-Reply-To: <DM8PR09MB7095F5719F77549CBE3E3012A5E0A@DM8PR09MB7095.namprd09.prod.outlook.com>
References: <20230824060502.c4798062cb19d4d35a5633ae@nifty.ne.jp>
 <20230824123131.390b4471915c963425c77608@nifty.ne.jp>
 <ZOcb9SKtMPTQfj/m@calimero.vinschen.de>
 <20230825174832.9ebae8112667d5d5411cb8db@nifty.ne.jp>
 <ZOiHkCWY7PK3livD@calimero.vinschen.de>
 <20230826042924.53b49a9f8372a9196a151425@nifty.ne.jp>
 <DM8PR09MB70951B220E8E94793560EB8EA5E2A@DM8PR09MB7095.namprd09.prod.outlook.com>
 <20230827084136.3f6ecbfec6aee89508ecb079@nifty.ne.jp>
 <DM8PR09MB7095F5719F77549CBE3E3012A5E0A@DM8PR09MB7095.namprd09.prod.outlook.com>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version: 1.0
X-Spam-Status: No, score=-5.1 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
 NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_PASS, SPF_PASS,
 TXREP autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
 server2.sourceware.org
X-BeenThere: cygwin@cygwin.com
X-Mailman-Version: 2.1.30
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-request@cygwin.com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=subscribe>
From: Takashi Yano via Cygwin <cygwin@cygwin.com>
Reply-To: Takashi Yano <takashi.yano@nifty.ne.jp>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces+archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>

On Mon, 28 Aug 2023 13:37:11 +0000
"Lavrentiev, Anton (NIH/NLM/NCBI) [C]" wrote:
> > You seems to reffer Linux man, however, this patch calls
> 
> I was referring to a known behavior.  Your patch gets to call send(s,"",0),
> which is technically a write call, and which in this case, falls into an undefined
> domain for its argument, and hence, may be expected to change without notice.
> That's all I was referring to.

https://learn.microsoft.com/en-us/windows/win32/api/winsock2/nf-winsock2-send
  Calling send with a len parameter of zero is permissible and will be treated
  by implementations as successful. In such cases, send will return zero as a
  valid value. For message-oriented sockets, a zero-length transport datagram
  is sent.

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple