I tried it with the debug info packages and malloc, and now there are
only a few X/gtk errors. Anyone have suggestions on how to approach
those? Maybe someone on the gtk-app-devel-list?
Thanks,
David
Julian Seward wrote:
Maybe you should set G_SLICE=always-malloc in the environment in orde
Hello,
Could anyone offer help or advice on debugging mysterious gtk-related memory
leaks and errors reported by valgrind when checking a threaded GTK+
program? The primary "potential" leak seems to be a sizeable chunk in
g_thread_init, and there are quite a few errors from various unknown
context
