From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: emacs-devel@gnu.org
Subject: Re: BLOCK_INPUT on Mac OS X
Date: Wed, 08 Sep 2004 20:38:44 +0900 [thread overview]
Message-ID: <wlacw13s8r.wl@church.math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <m1llfm2rnh.fsf-monnier+emacs@gnu.org>
>>>>> On Tue, 07 Sep 2004 08:27:59 -0400, Stefan <monnier@iro.umontreal.ca> said:
>> It seems to be looping in `emacs_read' called from `Fcall_process'.
>> Here's the backtrace. I believe this can also be reproducible in
>> other "SIGIO systems".
> Can you try the patch below? Beware, IIRC, if emacs_read is ever
> called somewhere where BLOCK_INPUT is set, this could introduce
> other problems.
It didn't work for me on both Mac OS X and GNU/Linux. Actually,
`read', which has not received any data, is silently restarted after
processing a signal because:
1. That's a default behavior in BSD systems. (Mac OS X)
2. SA_RESTART is set in `sys_signal' if POSIX_SIGNALS is
defined. (GNU/Linux)
If SA_RESTART is not set in `sys_signal', synchronous processes can be
quit on GNU/Linux (with your patch). But that breaks "Emacs mostly
works better with restartable system services" (from a comment in
`sys_signal').
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2004-09-08 11:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-03 12:41 BLOCK_INPUT on Mac OS X YAMAMOTO Mitsuharu
2004-09-03 13:51 ` Kim F. Storm
2004-09-03 16:48 ` Stefan Monnier
2004-09-04 9:07 ` YAMAMOTO Mitsuharu
2004-09-06 16:17 ` Stefan
2004-09-07 8:21 ` YAMAMOTO Mitsuharu
2004-09-07 12:27 ` Stefan
2004-09-08 11:38 ` YAMAMOTO Mitsuharu [this message]
2004-09-08 12:56 ` Stefan Monnier
2004-11-25 19:13 ` Dr. Carsten Bormann
2004-11-25 19:58 ` Stefan Monnier
2004-11-26 10:09 ` YAMAMOTO Mitsuharu
2004-11-26 14:24 ` POSIX_SIGNALS (was: BLOCK_INPUT on Mac OS X) Stefan Monnier
2004-11-29 10:12 ` YAMAMOTO Mitsuharu
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=wlacw13s8r.wl@church.math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=emacs-devel@gnu.org \
/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.