From: Sam Steingold <sds@gnu.org>
To: Andreas Schwab <schwab@suse.de>
Cc: emacs-devel@gnu.org
Subject: Re: busyloop in sigchld_handler
Date: Mon, 12 Mar 2007 13:53:25 -0400 [thread overview]
Message-ID: <45F59395.4010708@gnu.org> (raw)
In-Reply-To: <jehcsqtlak.fsf@sykes.suse.de>
Andreas Schwab wrote:
> Sam Steingold <sds@gnu.org> writes:
>
>> wait3 is a system call, which, when invoked in a loop, prevents the
>> kernel from doing anything else (in this case, sending SIGCHLD to
>> emacs). sleep allows the kernel some time to pass the signal.
>
> I don't find this explanation convincing at all. Since the system call is
> made _inside_ the signal handler, the signal is actually blocked here, so
> it cannot be delivered anyway.
yes, you are right.
what I should have said was that by making a system call in a busyloop,
emacs prevents the kernel from doing what it needs to do to the the
child so that wait3 will succeed.
Sam.
next prev parent reply other threads:[~2007-03-12 17:53 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
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 [this message]
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=45F59395.4010708@gnu.org \
--to=sds@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@suse.de \
/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.