[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: why "in_sighandler"?
From: |
YAMAMOTO Mitsuharu |
Subject: |
Re: why "in_sighandler"? |
Date: |
Mon, 21 Aug 2006 09:08:54 +0900 |
User-agent: |
Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.6 (Marutamachi) APEL/10.6 Emacs/22.0.50 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI) |
>>>>> On Sun, 20 Aug 2006 18:37:30 +0200, "Jan D." <address@hidden> said:
> I needed a variable that was only set when the signal handler is
> running.
I've got no response from you to my last message (*1) in the related
thread. So I'm not sure if you are for or against my suggestion about
undoing `in_sighandler'-related changes and just changing the order of
lock/unlock and BLOCK_INPUT/UNBLOCK_INPUT in the previous version of
BLOCK_INPUT_ALLOC/UNBLOCK_INPUT_ALLOC as follows.
#define BLOCK_INPUT_ALLOC \
do \
{ \
if (pthread_self () == main_thread) \
BLOCK_INPUT; \
pthread_mutex_lock (&alloc_mutex); \
} \
while (0)
#define UNBLOCK_INPUT_ALLOC \
do \
{ \
pthread_mutex_unlock (&alloc_mutex); \
if (pthread_self () == main_thread) \
UNBLOCK_INPUT; \
} \
while (0)
(*1) http://lists.gnu.org/archive/html/emacs-pretest-bug/2006-08/msg00161.html
YAMAMOTO Mitsuharu
address@hidden
- why "in_sighandler"?, Stefan Monnier, 2006/08/20
- Re: why "in_sighandler"?, Jan D., 2006/08/20
- Re: why "in_sighandler"?, Stefan Monnier, 2006/08/20
- Re: why "in_sighandler"?,
YAMAMOTO Mitsuharu <=
- Re: why "in_sighandler"?, Jan Djärv, 2006/08/21
- Re: why "in_sighandler"?, YAMAMOTO Mitsuharu, 2006/08/21
- Re: why "in_sighandler"?, Jan Djärv, 2006/08/21
- Re: why "in_sighandler"?, YAMAMOTO Mitsuharu, 2006/08/21
- Re: why "in_sighandler"?, Jan Djärv, 2006/08/21
- Re: why "in_sighandler"?, YAMAMOTO Mitsuharu, 2006/08/21
- Re: why "in_sighandler"?, Jan Djärv, 2006/08/21
- Re: why "in_sighandler"?, YAMAMOTO Mitsuharu, 2006/08/21
- Re: why "in_sighandler"?, Jan Djärv, 2006/08/22
- Re: why "in_sighandler"?, YAMAMOTO Mitsuharu, 2006/08/22