[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs hangs on Mac OS X
From: |
YAMAMOTO Mitsuharu |
Subject: |
Re: Emacs hangs on Mac OS X |
Date: |
Thu, 04 Jan 2007 08:14:54 +0900 (JST) |
>>>>> On Wed, 03 Jan 2007 22:39:00 +0100, Piet van Oostrum <address@hidden>
>>>>> said:
>>>>> YAMAMOTO Mitsuharu <address@hidden> (YM) wrote:
YM> Unfortunately, the information about the interrupted library function
YM> call seems to be already broken somehow. Could you try to get
YM> backtraces for a few instances of the hang? Hopefully we will get
YM> more detailed information.
> Here is a complete one. The `lowest' malloc appears to be called
> from localtime(). Mallocs from system library functions of course
> are much more difficult to prevent, if at all.
Thanks. Actually it is in the list (*1) of such library functions
detected (*2) so far on Darwin:
localtime, gmtime, getc, getaddrinfo, fwrite, mkstemp, mktime,
fclose, freeaddrinfo
(*1) http://lists.gnu.org/archive/html/emacs-pretest-bug/2006-07/msg00070.html
(*2) http://lists.gnu.org/archive/html/emacs-devel/2004-09/msg00074.html
I'll put BLOCK_INPUT at least around localtime/gmtime/mktime calls.
Among them, we cannot simply put BLOCK_INPUT around getaddrinfo
because it is called with immediate_quit == 1.
> IMHO this shows that is it quite bad to run the event loop in a
> signal handler.
IIUC, many of us agree that SYNC_INPUT is the right direction, but
after the next release.
YAMAMOTO Mitsuharu
address@hidden