[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Lockup
From: |
YAMAMOTO Mitsuharu |
Subject: |
Re: Lockup |
Date: |
Fri, 11 Aug 2006 17:49:13 +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 Fri, 11 Aug 2006 10:09:49 +0200, Jan Djärv <address@hidden> said:
>> That's not a problem because Gnome threads (non-main threads) never
>> execute pthread_mutex_(un)lock in the signal hander context.
> That does not help, the main thread executes in signal handler
> context sometimes. And in that case, both the Gnome thread and the
> signal handler may be executing (un)lock_mutex on the same mutex.
I don't think this causes a problem. The signal handler is executed
in the main thread that is different from the Gnome thread. And as I
quoted from IEEE Std 1003.1 in another message, a
pthread_mutex_(un)lock call in the signal hander context should work
as usual unless the signal interrupted an unsafe function.
The condition "unless the signal interrupted an unsafe function" is
too strict in reality. My guess was that it could be relaxed to
"unless the signal interrupted a pthread_mutex_(un)lock call for the
same mutex".
YAMAMOTO Mitsuharu
address@hidden
- Re: Lockup, (continued)
- Re: Lockup, Jan Djärv, 2006/08/01
- Re: Lockup, Jan Djärv, 2006/08/10
- Re: Lockup, YAMAMOTO Mitsuharu, 2006/08/10
- Re: Lockup, Jan Djärv, 2006/08/10
- Re: Lockup, YAMAMOTO Mitsuharu, 2006/08/10
- Re: Lockup, Jan Djärv, 2006/08/10
- Re: Lockup, YAMAMOTO Mitsuharu, 2006/08/10
- Re: Lockup, Jan Djärv, 2006/08/11
- Re: Lockup, YAMAMOTO Mitsuharu, 2006/08/11
- Re: Lockup, Jan Djärv, 2006/08/11
- Re: Lockup,
YAMAMOTO Mitsuharu <=
- Re: Lockup, David Kastrup, 2006/08/11
- Re: Lockup, YAMAMOTO Mitsuharu, 2006/08/11