Re: GtkListStore and Threads problems
- From: Lorena Salinas <lsalinas invap com ar>
- To: Peter Bloomfield <peterbloomfield bellsouth net>
- Cc: gtk-app-devel-list gnome org
- Subject: Re: GtkListStore and Threads problems
- Date: Thu, 16 Jun 2005 15:09:23 -0300
Using gdb I obtained this:
Starting program: /home/lore/Projects/hostThread/src/hostthread
[Thread debugging using libthread_db enabled]
[New Thread -1216235072 (LWP 13483)]
[New Thread -1218425936 (LWP 13484)]
Gtk-ERROR **: file gtksequence.c: line 760
(_gtk_sequence_node_find_by_pos): assertion failed: (node->parent !=
Program received signal SIGABRT, Aborted.
[Switching to Thread -1216235072 (LWP 13483)]
0xffffe410 in __kernel_vsyscall ()
On Thu, 2005-06-16 at 12:47 +0000, Peter Bloomfield wrote:
On 06/15/2005 07:55:45 PM Wed, Lorena Salinas wrote:
Here is a graphic to show where (I suppose) the problem is:
[ snip ]
T1: gtk_main() starts to read the 5 columns of row 1 from the
model shared with
the working thread (using gtk_tree_model_get())
T2: the working thread locks GTK main thread
gtk_main() is blocked in the middle of the loop to read the
I doubt that could happen. The main thread would have to drop
the lock in order for the working thread to get it, and I don't
believe it would do that in the middle of the supposed loop.
Instead, the working thread is blocked until the main thread
activity is done, and the lock is released.
You could get a little more detail on where the original problem
arises by running with --g-fatal-warnings under gdb a few times.
The stack traces will let you know what was going on at the time.
] [Thread Prev