Mercurial > pidgin
view doc/core-signals.dox @ 26879:7c58f6f50f16
Block/Unblock the signal handler when if it's unblocked/blocked.
Trying to unblock the handler when it has not been blocked yet causes a
'handler not blocked' error message. When this message is added in the
debug window, it goes into a mutex-lock from this line:
gtk_list_store_append(debug_win->store, &iter);
I have noticed this before on some occasions, where pidgin goes into a
freeze when doing something from a signal-handler causes a debug message
to be printed. Anyone knows why?
author | Sadrul Habib Chowdhury <imadil@gmail.com> |
---|---|
date | Sat, 16 May 2009 17:11:50 +0000 |
parents | e0613cf8c493 |
children | 4179ab2cfe1f |
line wrap: on
line source
/** @page core-signals Core Signals @signals @signal quitting @endsignals @see core.h <hr> @signaldef quitting @signalproto void (*quitting)(); @endsignalproto @signaldesc Emitted when libpurple is quitting. @endsignaldef */ // vim: syntax=c.doxygen tw=75 et