Re: glib or abiword b0rked?

As always, you are right.

  Marc

On Sun, 2009-02-15 at 10:46 -0500, Dominic Lachowicz wrote:
> g_thread_init() needs to be the first glib call made in your program.
> We call it after gtk_init_check(). We also seem to do an unnecessary
> gtk_init() in ap_UnixApp.cpp.
>
> Add g_thread_init() at the beginning of AP_UnixApp::main(), and I bet
> that things work.
>
> On Sun, Feb 15, 2009 at 10:35 AM, J.M. Maurer <uwog@uwog.net> wrote:
> >
> > On Sat, 2009-02-14 at 22:52 +0100, J.M. Maurer wrote:
> >> Since a few days I can't start AbiWord anymore. It's locking up on
> >> startup in glib's main loop code[1]. Does anyone have a clue what could
> >> be going on here before I start flaming glib?
> >>
> >> Debug trace attached. Any insights would be appreciated.
> >>
> >> Marc
> >>
> >> [1] Using the stock F10 and F11 alpha glibs.
> >
> > >From http://bugzilla.gnome.org/show_bug.cgi?id=571830 :
> >
> > Comment #1 from Marc Maurer (reporter, points: 9)
> > 2009-02-15 15:34 UTC [reply]
> > Not calling g_thread_init fixes the issue. However in practice that kinda
> > sucks, as we need thread support for several plugins (AbiWord's core is
> > non-threaded).
> >
> > Marc
> >
> >
>
>
>
Received on Sun Feb 15 17:35:19 2009