From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#22789: 25.1.50; In last master build https connections stop working Date: Mon, 07 Mar 2016 18:08:55 +0200 Message-ID: <83lh5uuv6w.fsf@gnu.org> References: <864mcyo14y.fsf@Lenovo-PC.i-did-not-set--mail-host-address--so-tickle-me> <86d1rhpvcq.fsf@realize.ch> <834mctbitq.fsf@gnu.org> <868u25p3m2.fsf@realize.ch> <83io18ahya.fsf@gnu.org> <86y4a3on6f.fsf@realize.ch> <87oaazg7fv.fsf@gnus.org> <86twkro0vr.fsf@realize.ch> <83d1rf8ifj.fsf@gnu.org> <86povfnm9r.fsf@realize.ch> <8337sa9865.fsf@gnu.org> <86bn6ynrbw.fsf@realize.ch> <83vb566v5b.fsf@gnu.org> <83d1razkmq.fsf@gnu.org> <86egbqkwsb.fsf@realize.ch> <86a8mekjrb.fsf@realize.ch> <83k2lhxria.fsf@gnu.org> <86egbo232a.fsf@realize.ch> <83si04wx18.fsf@gnu.org> <8660wz1azm.fsf@realize.ch> <861t7n1970.fsf@realize.ch> <86wppezn9f.fsf@realize.ch> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1457367035 31023 80.91.229.3 (7 Mar 2016 16:10:35 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 7 Mar 2016 16:10:35 +0000 (UTC) Cc: larsi@gnus.org, j_l_domenech@yahoo.com, 22789@debbugs.gnu.org To: Alain Schneble Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Mar 07 17:10:21 2016 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1acxja-0008Dy-Am for geb-bug-gnu-emacs@m.gmane.org; Mon, 07 Mar 2016 17:10:14 +0100 Original-Received: from localhost ([::1]:56753 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1acxjZ-0005Sf-LJ for geb-bug-gnu-emacs@m.gmane.org; Mon, 07 Mar 2016 11:10:13 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49978) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1acxjS-0005OA-Kh for bug-gnu-emacs@gnu.org; Mon, 07 Mar 2016 11:10:10 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1acxjO-0003zf-H9 for bug-gnu-emacs@gnu.org; Mon, 07 Mar 2016 11:10:06 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:41114) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1acxjO-0003zR-Et for bug-gnu-emacs@gnu.org; Mon, 07 Mar 2016 11:10:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1acxjO-0005AH-Ap for bug-gnu-emacs@gnu.org; Mon, 07 Mar 2016 11:10:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 07 Mar 2016 16:10:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 22789 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 22789-submit@debbugs.gnu.org id=B22789.145736694519788 (code B ref 22789); Mon, 07 Mar 2016 16:10:02 +0000 Original-Received: (at 22789) by debbugs.gnu.org; 7 Mar 2016 16:09:05 +0000 Original-Received: from localhost ([127.0.0.1]:38241 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84) (envelope-from ) id 1acxiR-000593-7C for submit@debbugs.gnu.org; Mon, 07 Mar 2016 11:09:05 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:58712) by debbugs.gnu.org with esmtp (Exim 4.84) (envelope-from ) id 1acxiN-00058Y-Cl for 22789@debbugs.gnu.org; Mon, 07 Mar 2016 11:09:02 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1acxiE-0003gY-67 for 22789@debbugs.gnu.org; Mon, 07 Mar 2016 11:08:54 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:46676) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1acxiE-0003gR-2m; Mon, 07 Mar 2016 11:08:50 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1263 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1acxiD-0001wA-8d; Mon, 07 Mar 2016 11:08:49 -0500 In-reply-to: <86wppezn9f.fsf@realize.ch> (message from Alain Schneble on Mon, 7 Mar 2016 09:49:00 +0100) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:114536 Archived-At: > From: Alain Schneble > CC: , , <22789@debbugs.gnu.org> > Date: Mon, 7 Mar 2016 09:49:00 +0100 > > > (I'll try to search the wisock documentation tomorrow to > > find some hints that lead in this direction, or maybe you know?) > > IIUC, this could be the reason why it fails: > > - The reader_thread in w32proc.c calls _sys_wait_connect which in turn > does a WSAEventSelect. > > - The documentation says: > > https://msdn.microsoft.com/en-us/library/windows/desktop/ms738573(v=vs.85).aspx > > The WSAAsyncSelect and WSAEventSelect functions automatically set a > socket to nonblocking mode. If WSAAsyncSelect or WSAEventSelect has > been issued on a socket, then any attempt to use ioctlsocket to set > the socket back to blocking mode will fail with WSAEINVAL. > > - So there /is/ a dependency between these calls. Unfortunately, I > couldn't see that ioctlsocket returns with WSAEINVAL in the scenarios > I tried. Yes, I know about this gotcha. It's just that it never produced any problems, and I never was able to see the ioctlsocket call fail with WSAEINVAL. > Could it be a multi-threading issue then? Multiple threads > accessing the same socket... Not sure I follow -- are you trying to explain why ioctlsocket doesn't fail as expected, or are you trying to explain some other phenomenon? > I don't see how both threads are synchronized. The synchronization is between reader_thread and sys_select. The latter runs in the main (a.k.a. "Lisp") thread, the same thread where sys_write is called. > The patch I sent would synchronize them through the FILE_CONNECT > flag, I think. Did I miss something? Well, that's not really "thread synchronization", but see my comments and questions there. Thanks.