>>>>> On Fri, 11 Aug 2006 08:36:39 +0200, Jan Djärv <[EMAIL PROTECTED]> said:
> A signal yes, but I was thinking of this scenario:
> A Gnome thread does malloc, gets the mutex lock and enters the
> malloc code. A signal is delivered (in the main thread as you point
> out) and enters malloc also. This situation is exactly like the one
> with the lockup, but here we can't use BLOCK_INPUT around the malloc
> related functions because they are in the Gnome code.
I think such a case just behaves like a usual mutual exclusion between
multiple threads: one thread acquires a mutex, and the other blocks
until it is released.
> I agree with your assumtion that the lockuo occurs because the
> signal handler and the interrupted therad are calling
> pthread_mutex_(un)lock for the same mutex. But BLOCK_INPUT does not
> help, because Gnome code does not have it.
That's not a problem because Gnome threads (non-main threads) never
execute pthread_mutex_(un)lock in the signal hander context.
YAMAMOTO Mitsuharu
[EMAIL PROTECTED]
_______________________________________________
emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
