Thanks for answer. But gtk_init() is actually the first function call in my application. It's still there. I'm totally confused by this.
Peter Lo?c Minier wrote: > On Fri, Jul 20, 2007, Zhu, Peter J wrote: >> As I run applications in maemo desktop, it's common that following >> is shown at lunch time. >> >> ***MEMORY-WARNING***: empathy[17367]: GSlice: g_thread_init() must be >> called before all other GLib functions; memory corruption due to late >> invocation of g_thread_init() has been detected; this program is >> likely to crash, leak or unexpectedly abort soon... > > This has been disabled in newer glib releases; you wont see it with > the upcoming 2.13.7. > >> But it seems never crashes. > > Well, in the past, it could result in random memory corruption, so > you might get a crash or not or unexpected results or basically > anything (even nothing). > >> If I use gnome_program_init(), app launches without the error >> message. But if I use gtk_init() as all other maemo native programs >> does, the error message showup. Any thoughts? > > You should try to init the glib threads system if you're going to use > threads; if you're not, don't. Please see the glib documentation of > g_threads_init() for an example on how to init the system properly. > > -- > Loïc Minier > > -- > Ubuntu-mobile mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile -- Ubuntu-mobile mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
