On Sun, Mar 27, 2005 at 01:26:26PM +0200, stian@xxxxxxxx wrote: > > I imagine select() doesn't block too long because my program is keeping > > the cpu so busy. Is it possible I'm screwing up my environment somehow > > that's causing this breakage? Am I using gtk_events_pending() > > incorrectly? What should I look for? > > Is this a threaded application? If so, you should check the > gdk_thread_leave/gdk_thread_enter balance and usage. As far as I know, this is not a threaded application. (I'm writing most of it from scratch and not using threads.) I am using an embedded perl interpreter though, of which I am suspect. Whenever I connect to my process with gdb I see messages like this: [Thread debugging using libthread_db enabled] [New Thread 1084529568 (LWP 7654)] LWP, perhaps only coincidentally, is the name of a perl module I'm using. I don't remember getting this message about threaded debugging before I plugged perl in. My problem is happening between perl routine invocations. each perl routine seems to block though, so I didn't think threads were a possibility. Do you have advise for me about how to test for threads being the source of my problem? The problem doesn't happen reliably right now, so I can't trust a solution that might just hide the problem. Thanks very much! - Ben _______________________________________________ gtk-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gtk-list
