Re: Locking again

[Carlos Morgado <chbm chbm nu>]

On 2002.08.09 12:19:42 +0100 Pawel Salek wrote:
> 
> On 2002.08.08 19:30 Emmanuel wrote:
>> The second part seems OK but this : why do we unlock gdk ? This part must 
>> be called from another thread (not the main one), i.e. a backend thread 
>> that should not have the gdk lock. So IMHO we should not lock gdk in the 
>> backend thread, only in the UI func (the idle handle); moreover that way 
>> we would avoid the unlocking of libmutt that seems rather risky.
> 
> 
> We need to drop locks to avoid deadlocks when the main thread tries to 
> lock. (I have some doubts now about the gdk lock).
> 
i was going to write a spiffy reply explaining with the gdk lock is
correct but then i remembered the diferent locking in diferent code paths.
but then again, if this was wrong you'd most probably trip it somehow
in the code path that call that ask_cert with no lock

-- 
Carlos Morgado - chbm(at)chbm(dot)nu - http://chbm.nu/ -- gpgkey: 0x1FC57F0A
http://wwwkeys.pgp.net/ FP:0A27 35D3 C448 3641 0573 6876 2A37 4BB2 1FC5 7F0A
Software is like sex; it's better when it's free. - Linus Torvalds