Re: Thread programming

[Justin Hopper <gus gusalmighty com>]

On Sun, 2003-06-15 at 07:03, Havoc Pennington wrote:
> On Sat, Jun 14, 2003 at 04:39:24PM -0700, Justin Hopper wrote: 
> > I've read the FAQ on thread programming, but I must be missing something
> > fundamental on how they work.
> >
> > Any help is greatly appreciated.
>
> Thread lockups are generally one thread stuck on a lock that's owned
> either by another thread or that was locked earlier by the same
> thread.

One thing I should mention is that I only have one thread running in the
background.  I assume the GUI runs in it's own thread, so that would
make a total of two threads.  I'm not doing anything in the GUI when it
locks up, but perhaps it is have trouble just reading the label that was
updated in the background thread.  I should also mention that the
background thread never locks up either, it keeps trucking along.

Can anyone confirm whether or not doing simple thread programming will
work while using libglade?

Thanks as always.

> So the first debugging step is to get a backtrace from the lockup,
> which shows the problematic lock and the second lock attempt.
> The first lock attempt is what you have to figure out, and then you
> understand the problem.
>
> A guess from your source - libglade isn't actually thread safe I don't
> think, only plain GTK.
>
> Havoc
>
> _______________________________________________
> gtk-app-devel-list mailing list
> gtk-app-devel-list gnome org
> http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
-- 
Justin Hopper <gus gusalmighty com>