[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#5723: 23.1.94; make-network-process and emacs hangs

From: YAMAMOTO Mitsuharu
Subject: bug#5723: 23.1.94; make-network-process and emacs hangs
Date: Fri, 19 Mar 2010 10:47:05 +0900
User-agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (Shij┼Ź) APEL/10.6 Emacs/22.3 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)

>>>>> On Thu, 18 Mar 2010 18:06:20 +0900, YAMAMOTO Mitsuharu <address@hidden> 
>>>>> said:

>>> If your case blocks at `connect', then it can't be quit with C-g
>>> regardless of SYNC_INPUT on those ports/systems, because atimer is
>>> turned off during the `connect' call.

>> Why is the timer turned off around connect?  Handling SIGALARM
>> during connect doesn't seem much different from handling SIGIO.

> I think your argument makes sense.

The current code closes the socket and call `connect' again if
(blocking) `connect' is interrupted by a signal.

2004-11-09  Kim F. Storm  <address@hidden>

        * process.c (Fmake_network_process): Remove kludge for interrupted
        connects on BSD.  If connect is interrupted, just close socket and
        start over rather than sleeping and retry with same socket.


UNIX Network Programming (Richard Stevens et al.) says "What we must
do in this scenario is call /select/" (Section 16,5, Volume 1 third

Also, POSIX says:

  If connect() is interrupted by a signal that is caught while blocked
  waiting to establish a connection, connect() shall fail and set
  errno to [EINTR], but the connection request shall not be aborted,
  and the connection shall be established asynchronously.


  When the connection has been established asynchronously, select()
  and poll() shall indicate that the file descriptor for the socket is
  ready for writing.


Perhaps we should try this, not just removing `turn_on_atimers' calls.

                                     YAMAMOTO Mitsuharu

reply via email to

[Prev in Thread] Current Thread [Next in Thread]