Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
What's new
10
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Open sidebar
emacs
emacs
Commits
bd80a886
Commit
bd80a886
authored
Nov 04, 2010
by
YAMAMOTO Mitsuharu
Committed by
Chong Yidong
Nov 04, 2010
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Backport 2010-03-25T08:56:15Z!mituharu@math.s.chiba-u.ac.jp from trunk
parent
c2e124a9
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
5 additions
and
14 deletions
+5
-14
src/ChangeLog
src/ChangeLog
+5
-0
src/process.c
src/process.c
+0
-14
No files found.
src/ChangeLog
View file @
bd80a886
2010-03-25 YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
* process.c (Fmake_network_process): Don't call turn_on_atimers around
`connect' (Bug#5723).
2010-03-25 Helmut Eller <eller.helmut@gmail.com>
* process.c (Fmake_network_process): Call `select' for interrupted
...
...
src/process.c
View file @
bd80a886
...
...
@@ -3654,23 +3654,9 @@ usage: (make-network-process &rest ARGS) */)
immediate_quit = 1;
QUIT;
/* This turns off all alarm-based interrupts; the
bind_polling_period call above doesn't always turn all the
short-interval ones off, especially if interrupt_input is
set.
It'd be nice to be able to control the connect timeout
though. Would non-blocking connect calls be portable?
This used to be conditioned by HAVE_GETADDRINFO. Why? */
turn_on_atimers (0);
ret = connect (s, lres->ai_addr, lres->ai_addrlen);
xerrno = errno;
turn_on_atimers (1);
if (ret == 0 || xerrno == EISCONN)
{
/* The unwind-protect will be discarded afterwards.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment