On 3/26/07, Murray Cumming <[EMAIL PROTECTED]> wrote: > If you get glib errors, try debuggin with --g-fatal-warnings, or with a > breakpoing on g_log. Then you'll get a backtrace at the relevant point.
You can also set Glib-based applications to abort when warnings are issued by setting the G_DEBUG environment variable to various values. see http://developer.gnome.org/doc/API/2.0/glib/glib-running.html (I seem to remember not having much luck in the past using commandline switches like --g-fatal-warnings, but I can't try it out now...) > valgrind's memcheck is also incredibly helpful. Trust us on this. You > won't regret trying it. agreed -- jonner _______________________________________________ gtkmm-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gtkmm-list
