From: David Kastrup <dak@gnu.org>
To: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: busyloop in sigchld_handler
Date: Sun, 11 Mar 2007 20:43:13 +0100 [thread overview]
Message-ID: <85fy8bpnvy.fsf@lola.goethe.zz> (raw)
In-Reply-To: <m3ejnv1seq.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "Sun\, 11 Mar 2007 20\:39\:25 +0100")
storm@cua.dk (Kim F. Storm) writes:
> Sam Steingold <sds@gnu.org> writes:
>
>> GNU Emacs 22.0.95.2 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of
>> 2007-03-11 on loiso
>>
>> I have been observing the following behavior:
>> emacs hangs in sigchld_handler waiting for the child process to
>> terminate:
>>
>> do
>> {
>> errno = 0;
>> pid = wait3 (&w, WNOHANG | WUNTRACED, 0);
>> }
>> while (pid < 0 && errno == EINTR);
>
>> I fixed the problem with the following patch:
>
> Absolutely brilliant! I can confirm that it works.
>
> But can you explain why it works?
> And why the problem primarily hit M-x compile.
>
> Does the fix cause a 1 second delay for other sub-processes ?
>
>>
>> Index: process.c
>> ===================================================================
>> RCS file: /sources/emacs/emacs/src/process.c,v
>> retrieving revision 1.500
>> retrieving revision 1.501
>> diff -u -w -u -b -w -i -B -r1.500 -r1.501
>> --- process.c 1 Mar 2007 10:17:41 -0000 1.500
>> +++ process.c 11 Mar 2007 18:16:50 -0000 1.501
>> @@ -6497,6 +6497,7 @@
>> /* Keep trying to get a status until we get a definitive result. */
>> do
>> {
>> + sleep (1);
>> errno = 0;
>> pid = wait3 (&w, WNOHANG | WUNTRACED, 0);
>> }
>
Wouldn't it make more sense to do
for (;;) {
errno = 0;
pid = wait3(&w, WNOHANG | WUNTRACD, 0);
if (!(pid < 0 && errno == EINTR))
break;
sleep(1);
}
That way, we don't get an obligatory sleep if things happen to work
without it.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2007-03-11 19:43 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 18:33 busyloop in sigchld_handler Sam Steingold
2007-03-11 19:39 ` Kim F. Storm
2007-03-11 19:43 ` David Kastrup [this message]
2007-03-11 19:51 ` Sam Steingold
2007-03-11 20:42 ` Kim F. Storm
2007-03-11 21:06 ` Sam Steingold
2007-03-11 21:14 ` Eli Zaretskii
2007-03-11 21:17 ` Sam Steingold
2007-03-11 21:51 ` Eli Zaretskii
2007-03-11 22:21 ` Sam Steingold
2007-03-12 4:24 ` Richard Stallman
2007-03-12 7:00 ` David Kastrup
2007-03-13 2:43 ` Richard Stallman
2007-03-11 22:27 ` Andreas Schwab
2007-03-11 22:30 ` Kim F. Storm
2007-03-12 17:37 ` Andreas Schwab
2007-03-12 17:53 ` Sam Steingold
2007-03-12 18:45 ` Andreas Schwab
2007-03-12 18:57 ` Sam Steingold
2007-03-12 19:28 ` Andreas Schwab
2007-03-12 19:34 ` David Kastrup
2007-03-12 21:36 ` Andreas Schwab
2007-03-13 7:29 ` David Kastrup
2007-03-13 9:29 ` Andreas Schwab
2007-03-13 22:19 ` David Kastrup
2007-03-13 22:28 ` Andreas Schwab
2007-03-13 22:54 ` David Kastrup
2007-03-13 23:17 ` Andreas Schwab
2007-03-14 7:06 ` David Kastrup
2007-03-14 9:24 ` Kim F. Storm
2007-03-14 10:00 ` David Kastrup
2007-03-14 10:22 ` Andreas Schwab
2007-03-14 10:52 ` David Kastrup
2007-03-14 11:01 ` Andreas Schwab
2007-03-14 11:12 ` David Kastrup
2007-03-14 12:29 ` Andreas Schwab
2007-03-14 10:01 ` Andreas Schwab
2007-03-14 13:15 ` Kim F. Storm
2007-03-14 13:41 ` Andreas Schwab
2007-03-14 14:10 ` Kim F. Storm
2007-03-14 14:12 ` Andreas Schwab
2007-03-14 15:02 ` Kim F. Storm
2007-03-14 16:34 ` Andreas Schwab
2007-03-16 9:34 ` Kim F. Storm
2007-03-16 9:59 ` Andreas Schwab
2007-03-14 3:24 ` Richard Stallman
2007-03-14 17:34 ` David Kastrup
2007-03-26 1:47 ` YAMAMOTO Mitsuharu
2007-03-26 2:02 ` Sam Steingold
2007-03-26 2:17 ` YAMAMOTO Mitsuharu
2007-03-28 10:02 ` Kim F. Storm
2007-03-28 15:19 ` Chong Yidong
2007-03-28 15:25 ` Andreas Schwab
2007-03-28 15:33 ` Kim F. Storm
2007-03-28 15:37 ` Andreas Schwab
2007-03-28 20:18 ` Kim F. Storm
2007-03-29 17:59 ` Richard Stallman
2007-03-28 15:30 ` Alfred M. Szmidt
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85fy8bpnvy.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=storm@cua.dk \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.