Re: GLib-GObject-CRITICAL

[Murray Cumming <murrayc murrayc com>]

> First random shot in the dark is that you're probably overwriting
> memory somewhere that you shouldn't be.  Start looking for places
> where you may have followed an invalid pointer or run of the ends of
> an array.
> 
> If you still can't find it, send some code that compiles and exhibits
> the problem.

It's also a very good idea to try debugging with a breakpoint on
g_log(), and using valgrind's memcheck.

-- 
Murray Cumming
murrayc murrayc com
www.murrayc.com
www.openismus.com