Re: A bug in Gtk+?

[Stefan Kost <ensonic hora-obscura de>]

Are you sure?

gdk_threads_init is just:

 if (!g_thread_supported ())
   g_error ("g_thread_init() must be called before gdk_threads_init()");

 gdk_threads_mutex = g_mutex_new ();
 if (!gdk_threads_lock)
   gdk_threads_lock = gdk_threads_impl_lock;
 if (!gdk_threads_unlock)
   gdk_threads_unlock = gdk_threads_impl_unlock;

what happends when you add gdk_thread_enter() before entering 
gtk_main(); and gdk_threads_leave() before the return(0);

Stefan

> Hello,
>   In a gtk+ app of mine, i was facing strange dead-locks problems. I
> was astonished to see that just removing the call to gdk_threads_init,
> the problems vanished. I am attaching a sample test program that
> re-produces the same problem. It seems more like a bug in the gtk+
> rather than my logic. Please have a look at it and tell me it that's
> the case so I can file it as a bug. I just dont want to file another
> 'NOT A BUG' :)
>  
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> gtk-app-devel-list mailing list
> gtk-app-devel-list gnome org
> http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list