Re: Debugging a (probably) GladeXML-related segfault



On Mon, Mar 13, 2006 at 10:24:19PM +0100, Murray Cumming wrote:
> On Mon, 2006-03-13 at 17:03 +0100, Jan Oberländer wrote:
> > Reloading plugin >Hreader<
> > Reloading plugin >Hgldisplay<
> > Reloading plugin >Hsaver<
> > Reloading plugin >Skeletonplugin<
> > 
> > (mvis:20067): GLib-GObject-WARNING **: cannot register existing type `GladeXML'
> 
> It seems to be trying to initialize libglade twice, though that should
> be allowed. Maybe it's not.

In that case, would it help to get libglade to initialize somewhere in
the main thread as well?  Or, is there any explicit way to keep it from
re-initializing?

> > (mvis:20067): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
> 
> If it's been initialized once then I wouldn't expect this problem.
> 
> It might help to debug this with --g-fatal-warnings to get a backtrace
> of the program at the time that the first warning happens.

I've done that as well; the thing is, both warnings and the segfault
happen inside my call to Gnome::Glade::Xml::create_from_buffer().

Thanks for your help,

Jan

-- 

+-------------------------------------+
| Jan Oberländer   <mindriot gmx net> |
|         PGP key: 0xC4D910E3         |
+-------------------------------------+

Attachment: signature.asc
Description: Digital signature



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]