From: Patrick Bernaud <patrickb@chez.com>
To: David Pirotte <david@altosw.be>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: guile-gnome2 - Segmentation fault
Date: Tue, 6 Jul 2010 17:37:57 +0200 [thread overview]
Message-ID: <19507.19925.986008.455824@vagabond.local> (raw)
In-Reply-To: <20100706031543.3ff5a433@rascar>
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
next prev parent reply other threads:[~2010-07-06 15:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 21:33 guile-gnome2 - Segmentation fault David Pirotte
2010-07-01 10:58 ` Andy Wingo
2010-07-02 16:32 ` David Pirotte
2010-07-03 17:25 ` Andy Wingo
2010-07-03 19:24 ` David Pirotte
2010-07-05 0:54 ` David Pirotte
2010-07-06 6:15 ` David Pirotte
2010-07-06 15:37 ` Patrick Bernaud [this message]
2010-07-07 2:53 ` David Pirotte
2010-07-08 19:57 ` Andy Wingo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19507.19925.986008.455824@vagabond.local \
--to=patrickb@chez.com \
--cc=david@altosw.be \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).