[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: BLOCK_INPUT on Mac OS X
|
From: |
YAMAMOTO Mitsuharu |
|
Subject: |
Re: BLOCK_INPUT on Mac OS X |
|
Date: |
Wed, 08 Sep 2004 20:38:44 +0900 |
|
User-agent: |
Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 Emacs/21.3.50 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI) |
>>>>> On Tue, 07 Sep 2004 08:27:59 -0400, Stefan <address@hidden> 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
address@hidden