On Tue, 2005-04-05 at 08:41 +1000, Jonathan Matthew wrote: > On Mon, Apr 04, 2005 at 06:44:10PM +0200, Oliver Lemke wrote: > > After looking at your code (and reading the gdk threads docs) I'm a bit > > confused. Is it not necessary to call gdk_threads_init after > > gdk_threads_set_lock_functions in your rb_threads_init function? > > In theory, yes, but all gdk_threads_init does is set up the default > locking functions. It does appear to be harmless, so I'll add a > gdk_threads_init call to rb_threads_init just in case. The gdk docs emphasize the calls to all the init funcs strongly, that's why I thought it might be important to call them. > > For sure you know this stuff better than me, but the docs say that every > > process that wants to use threads has to call gdk_threads_init before > > entering the gtk main loop. Moreover, it's written that g_thread_init > > must be called before this function. Where is this done in rb? > > I had to use gdb to find this out, but gnome_program_init calls > g_thread_init. Ah, ic. Actually, I thought that libgnome is doing something in that respect. But stupidly I only grepped for gdk_threads_init in the libgnome sources. :-( Thanks for your info. -- so long, oliver Public GPG Key: http://www.core-dump.info/olemke-public.asc Fingerprint: 2389 0B2C 1AA8 4E3E D5AD 3B72 00DB ABDC 73ED C558
Attachment:
signature.asc
Description: This is a digitally signed message part