GLib 2.23.1 is now available for download at:
ftp://ftp.gtk.org/pub/glib/2.23/
http://download.gnome.org/sources/glib/2.23/
md5 sums:
fb637f6122690254097d0b6d470f6ed3 glib-2.23.1.tar.bz2
ea32c834a8c7b166e05aeaaa41a021f4 glib-2.23.1.tar.gz
sha1 sums:
Hmm...
I just found theme on my box, that caused problem too (Raleigh). Do
you see any warnings/errors in console while running?
(a.out:51454): Gtk-CRITICAL **: gtk_paint_box: assertion `GTK_IS_STYLE
(style)' failed
If yes, following may help...
(works now with all themes i have + proper
I am the strangest thing with some C code I'm writing that uses glib.
I was having some issues with seg faults and/or corruption, so I
decided to try and track where it was happening by throwing a couple
of quick g_debug statements into my code.
But this had the effect of causing the error to go
Hi, Michael!
Nothing strange -- g_debug calls changed stack layout in your
functions, and crash disappeared. Try using [f]printf instead
of g_debug, and, very likely, you'll get same effect. I've seen
that thousand times.
In your case, it is better to use debugger, like gdb, to see
backtrace at
Any ideas?
Most likely you cause a heap corruption in your code, which then can
cause seemingly random behaviour later in the program's execution.
(For instance such randomness that adding some g_debug() calls seem to
fix your problem.) Use valgrind.
--tml
GTK+ 2.19.2 is now available for download at:
ftp://ftp.gtk.org/pub/gtk/2.19/
http://download.gnome.org/sources/gtk+/2.19/
md5 sums:
c7b4997a13f644a45349a6a22a21e577 gtk+-2.19.2.tar.bz2
c6a5c7431d610b820f8aefdb2055e178 gtk+-2.19.2.tar.gz
sha1 sums:
c4e04159f105215314933f6b9bebf4b987c51b28
