> On Sat, Dec 05, 2009 at 10:46:16PM +0200, George Danchev <danc...@spnet.net> was heard to say: > > Hi, the following patch fixes that crash on amd64. > > > > --- src/gtk/gui.cc.orig 2009-12-05 22:43:21.000000000 +0200 > > +++ src/gtk/gui.cc 2009-12-05 22:43:40.000000000 +0200 > > @@ -1769,7 +1769,7 @@ > > if(!gtk_init_check(&argc, &argv)) > > return false; > > > > - Glib::init(); > > +// Glib::init(); > > Odd, so Glib::init invokes thread_init, but only on amd64? The docs > don't suggest this at all. thread_init's documentation shows how to > check whether it's already been called, though, so maybe I can just do > that.
My impression is that Glib::thread_init() invokes Glib::init() on all arches, but calling them both is only fatal on certain ones, which does not mean it is correct to call both Glib::init() and Glib::thread_init() on arches where it is not fatal. I forgot to clarify that the above patch (which only invokes Glib:thread_init() ) works for me on x86 too and amd64. [1] only thread_init() is called, which should be enough: http://library.gnome.org/devel/glibmm/stable/thread_2thread_8cc- example.html#a11 -- pub 4096R/0E4BD0AB <people.fccf.net/danchev/key pgp.mit.edu> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
