Hi Patrick,
[This is good news Andy !!]
Fantastic, thank you so much for bringing this info to my knowledge, it solves a
problem that i have had for quite a long time: I can't believe it yet! I wish
I'd
know about that right from the beginning [it's always like that :-)]
I think it should be added to the doc, with a special well visible
note, so
that it will be raised by google for future guile-gnome 'users': I
googled a
lot the last few years [but then I am obviously not good @ it :-)] and
never
found this link!!
Many thanks again,
Are you also developing with guile-gnome?
Cheers,
David
;; --
Le Tue, 6 Jul 2010 17:37:57 +0200,
Patrick Bernaud <patri...@chez.com> a écrit :
> Hi David,
> David Pirotte writes:
> > [...]
> > Does it crashes for you [any guile-gnome user willing to try?] too?
> Yes it does for me too.
> In versions of gtk >= 2.11, tree iterators (GtkTreeIter) are allocated
> through the GSlice memory allocator
> (http://library.gnome.org/devel/glib/stable/glib-Memory-Slices.html)
> while current guile-gnome is allocating them through the more general
> memory-handling g_malloc() and friends.
> Freeing one item allocated with g_malloc() (what guile-gnome does)
> with GSlice func (what GTK does) has the consequences you
> experimented.
> GtkTextIter is also concerned by the problem and maybe other types
> too.
> Until guile-gnome is updated, set the environment variable G_SLICE to
> 'always-malloc'
> (http://library.gnome.org/devel/glib/stable/glib-running.html#G_SLICE)
> and it should be ok.
> Regards,
> Patrick
