On Apr 8, 2005 5:26 PM, Peter Bloomfield <[EMAIL PROTECTED]> wrote: > On 04/08/2005 10:22:59 AM, Vivien Malerba wrote: > [ snip ] > > However, still from the same function, I then destroy the custom > > widget, and the whole application locks. A backtrace from gdb attached > > to the locked application gives: > > (gdb) bt > > #0 0x00ad37a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 > > #1 0x00d3913e in __lll_mutex_lock_wait () from > > /lib/tls/libpthread.so.0 > > #2 0x00d35d9b in _L_mutex_lock_32 () from /lib/tls/libpthread.so.0 > > #3 0x00000000 in ?? () > > Perhaps you're trying to use gdk_threads_enter recursively? Instant > lock... > >
I did not use gdk_threads_enter()/gdk_threads_leave() when I posted the message. I fact I have managed to make it work somehow by adding gdk_threads_enter() before the first line of code in my idle function and gdk_threads_leave() at the end. Strange considering I have obly one thread! I'm still trying to see if there are some strange behaviours with that situation... Thanks, Vivien _______________________________________________ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
