Re: GTK Thread help

[Owen Taylor <otaylor redhat com>]

"Edward J. March Jr." <emarch@eagle.ais.net> writes:

> Here is a sample Run
> (micron root)23:58:55/gtk+-1.1.5/gtk/.libs>./testthreads
> 
> Gdk-ERROR **: an x io error occurred
> aborting...
> IOT trap/Abort
> (micron root)00:01:47/gtk+-1.1.5/gtk/.libs>Gdk-Message (recursed):
> ** ERROR **: sigsegv caught
> aborting...
>  
> 
> running testdnd -- clicking on the X (close window in KDE 1.0)
> 
> (micron root)00:02:20/gtk+-1.1.5/gtk/.libs>./testdnd
> 
> Gdk-ERROR **: an x io error occurred
> aborting...
> IOT trap/Abort
> (micron root)00:02:34/gtk+-1.1.5/gtk/.libs>  
> 
> Both apps in  .libs and gtk directory do the sme thing .. 

This looks like you are linking against old non thread-safe
GTK+ libraries. If you previously compiled GTK+-1.1.5
you'll have to do a "make install" and run ldconfig.
 
> All my libraries are copied to /usr/local/lib and also to /usr/lib

You're much better off just doing a "make install". (If you've
been fooling around with moving files manually like this, you
might be well-advised to remove all traces of GTK+ 
off your system and starting over from scratch)

> On Sat, 5 Dec 1998, Edward J. March Jr. wrote:
> 
>:>
>:>I compiled gtk --with-threads=posix
>:>In the hope of using GTK for a threaded project.
>:>However  testthreads in the /gtk-1.1.5/gtk/testthreads
>:>crashes before running till completion. WHY??? 
>:>The error is Gtk-Message (recursive)
>:>
>:>What is the normal way to have a some task in the background
>:>add text or data to GtkWidgets ?? Seems like a processes is too complex and
>:>has the non-memory share problem. If not threads what other method can I
>:>use ?  What does GIMP use ? and How ? 

When you are updating based on IO, gdk_input_add() is often
the right thing to use. In fact, even when doing computation,
forking, and communicating with your child via a pipe may
be a easier thing than threads.

Regards,
                                        Owen