unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@iro.umontreal.ca, rtt@dasyatidae.com, emacs-devel@gnu.org
Subject: Re: ai_flags in calls to getaddrinfo, broader call for reproducibility check
Date: Mon, 11 Jan 2021 22:02:24 +0100	[thread overview]
Message-ID: <878s8z2nmn.fsf@gmail.com> (raw)
In-Reply-To: <83y2gzdx4o.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 11 Jan 2021 22:41:43 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Robert Pluim <rpluim@gmail.com>
>> Cc: Robin Tarsiger <rtt@dasyatidae.com>,  Eli Zaretskii <eliz@gnu.org>,
>>   emacs-devel@gnu.org
>> Date: Mon, 11 Jan 2021 21:12:44 +0100
>> 
>> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> 
>> >> Because the select implementation on windows does a one-byte readahead
>> >> to see if data is available, which breaks UDP. I had a patch at one
>> >> point to fix this, but I remember Eli not being very enthusiastic
>> >> about it. Iʼve attached what I think is the right version below (my
>> >> windows box died, so I can't be sure)
>> >
>> > How 'bout installing it but make it conditional on some config var?
>> > And maybe set that config var if/when a UDP socket is requested?
>> 
>> I guess thatʼs possible. Iʼve now found the actual patch. If Eli
>> thinks itʼs worth persuing, I can make it conditional, unless someone
>> wants to spare me the trouble of setting up a working Windows dev
>> environment :-).
>
> My main concern is who will investigate the bug reports about this,
> debug the problem, find fixes, etc.?  If you or Stefan or someone else
> volunteers, then please go ahead.  But if you count on me, implicitly
> or otherwise, then let's wait for a volunteer to emerge.  Especially
> in this area, where I'm far from being an expert.  Don't forget that
> two threads are involved in this game, which provides ample
> opportunity for exciting deadlocks and races, apart of
> network-specific issues.

I donʼt think thereʼs too much scope for thread-induced breakage, but
this is threads, so that statement might well come back to bite me :-)

> (I'm sorry, but too often lately I'm the only one who gets to debug
> and fix MS-Windows specific issues; if I don't do that, the build
> remains broken for days.  It's too much of a burden on me, and takes a
> significant enough fraction of my time that I must be very cautious
> with adventures.  Otherwise, I won't be able to do my main job here,
> which I already am barely capable of doing.)

I can understand this. I donʼt run windows except in a VM, and the
whole reason for the patch initially was to reduce the differences in
the network implementation between different platforms (you can call
this an obsessive desire for parity on my part if you like).

If the cost of making udp processes work on Windows is not worth it,
then we can stop here.

Robert



  parent reply	other threads:[~2021-01-11 21:02 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-31 15:06 ai_flags in calls to getaddrinfo Eli Zaretskii
2020-12-31 22:40 ` Robin Tarsiger
2021-01-01  7:43   ` Eli Zaretskii
2021-01-01 11:40     ` Robin Tarsiger
2021-01-01 12:04       ` Robin Tarsiger
2021-01-01 12:48       ` Eli Zaretskii
2021-01-02  0:19         ` Robin Tarsiger
2021-01-03 16:00   ` Eli Zaretskii
2021-01-11 10:47     ` ai_flags in calls to getaddrinfo, broader call for reproducibility check Robin Tarsiger
2021-01-11 12:42       ` Robert Pluim
2021-01-11 15:25       ` Eli Zaretskii
2021-01-11 15:47         ` Robert Pluim
2021-01-11 16:44           ` Eli Zaretskii
2021-01-11 17:07             ` Robin Tarsiger
2021-01-11 17:53               ` Robert Pluim
2021-01-11 18:30                 ` Robin Tarsiger
2021-01-11 18:42                   ` Robert Pluim
2021-01-11 19:28                     ` Stefan Monnier
2021-01-11 20:12                       ` Robert Pluim
2021-01-11 20:41                         ` Eli Zaretskii
2021-01-11 20:55                           ` Stefan Monnier
2021-01-11 21:02                           ` Robert Pluim [this message]
2021-01-11 21:09                             ` Lars Ingebrigtsen
2021-01-11 21:15                               ` Robert Pluim
2021-01-11 22:42                                 ` Lars Ingebrigtsen
2021-01-12  9:40                                   ` Robert Pluim
2021-01-12 12:49                                     ` Lars Ingebrigtsen
2021-01-12 13:04                                       ` Robert Pluim
2021-01-12 14:08                                         ` Lars Ingebrigtsen
2021-01-12 14:29                                           ` Robert Pluim
2021-01-12 18:06                                             ` Lars Ingebrigtsen
2021-01-12 15:14                                       ` Stefan Monnier
2021-01-12 15:45                                         ` Eli Zaretskii
2021-01-12  3:29                             ` Eli Zaretskii
2021-01-11 20:46                 ` Eli Zaretskii
2021-01-11 20:56                   ` Robert Pluim
2021-01-12 15:01                     ` Eli Zaretskii
2021-01-12 15:36                       ` Robert Pluim
2021-01-12 15:42                       ` Eli Zaretskii
2021-01-12 16:00                         ` Robert Pluim
2021-01-12 16:05                           ` Eli Zaretskii
2021-01-12 17:56                             ` Robert Pluim
2021-01-11 19:32           ` Basil L. Contovounesios
2021-01-11 20:19             ` Robert Pluim
2021-01-11 23:57           ` Andy Moreton
2021-01-12  9:44             ` Robert Pluim
2021-01-12 11:56               ` tomas
2021-01-01 10:59 ` ai_flags in calls to getaddrinfo Lars Ingebrigtsen
2021-01-01 12:50   ` Eli Zaretskii
2021-01-02  5:40     ` Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878s8z2nmn.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rtt@dasyatidae.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).