Re: bug, 0.9.2 race in open_mailbox

[Ian Campbell <ijc25 cam ac uk>]

In main.c (I think) we call gtk_main wi th the lock held.. I unlocks it
before checking for pending activities and stuff and takes care of grabing
it again etc

I have just cleared a point of confusion I had with the people on
gnome-devel... Calls to gtk_signal_emit called from a thread also need to
take the lock first. This is probably where we are going wrong.

I think in general terms we are doing things the correct way - but I would
like to read through the code next week (Im away over the w/e) and make
sure everything is as I think it should be.


On Fri, 18 Aug 2000, Pawel Salek wrote:

> 
> On 17 Aug 2000 18:06 Ian Campbell wrote:
> > gdk_threads_enter grabs a global gdk lock, which must be held before
> doing
> > any gdk (ie X) operation.
> 
> Yes, this sounds correct, but then gdk_threads_enter() are in a wrong
> place because any gdk operation called from gtk_main would lock, wouldn't
> it? My impression is that it works now because all(?) of us use gdk with
> threading disabled (at least that's what testthreads program from gtk told
> me). If this was try I wouldn't rely too much on these functions.
> 
> Pawel
> PS. I think we could move this discussion to balsa-list - when there is
> any follow up, of course.
> 
> 
>