Re: Gtk-CRITICAL - getting meaningful information

[Claudio Saavedra <csaavedra gnome org>]

On Fri, 2010-06-11 at 12:50 +1000, Mick wrote:
> Is there any way to get something meaningful that will point to a real
> world location. I assume the :2621 points to a location in the code
> but
> two successive compilations with the source unchanged (eg: make clean;
> make; make install; run; make clean; make; make install; run) results
> in a different number. 

The number after the process name is the PID, not the code line where
the crash happened.

If you want to find out where your critical warnings are coming from,
you can run your program under gdb and set the environment variable
G_DEBUG to fatal-criticals

 $ gdb myprogram
 gdb> set env G_DEBUG=fatal-criticals
 gdb> run

once it crashes,

 gdb> backtrace


And you'll see where the crash happened by inspecting the stacktrace.

Then I would suggest reading a bit on the critical messages, usually
they are self-explanatories. For instance, 

  assertion `GTK_IS_TEXT_BUFFER (buffer)' failed

Means that buffer variable is not pointing to a GtkTextBuffer, which
either means that you already disposed it or that you never initialized
it to be one.

Claudio

-- 
Claudio Saavedra <csaavedra gnome org>