* Alaric Snell-Pym ala...@snell-pym.org.uk [110216 10:41]:
When a community agrees it'd be cool to do something on a regular basis,
to begin with, there's a lot of enthusiasm and volunteering, so things
go well.
However, a crucial point comes at which producing that thing starts to
become
On 02/28/11 14:10, Christian Kellermann wrote:
The Gazette is reaching that point, and I want to save it.
After all the wonderful responses to this thread and the awesome
amount of work that it has triggered. I wondered who is working on
a new issue now?
This feels like people that have
I'm trying to write bindings to the Clutter UI toolkit, but I'm
hitting segfaults when building a shared library. I've essentialized
the issue to the following code:
http://gist.github.com/847871#file_clutter.scm
The C is more or less copied pasted from the Clutter docs, and it
compiles
From: Evan Hanson vnh...@gmail.com
Subject: [Chicken-users] Segfaults with shared library, foreign code
Date: Mon, 28 Feb 2011 13:59:05 -0600
FWIW it seems that removing any reference to clutter_text solves the
problem, which might point to Clutter as the troublemaker, BUT both
files above
I've attached LD_DEBUG tails for all and libs as well as a gdb log,
though at this point I'm fairly sure this is a Clutter issue. What's strange
to me is that preloading the library works:
$ LD_PRELOAD=`pwd`/clutter.so csi
Admittedly I've no idea why that in particular should work or what
From: Evan Hanson vnh...@gmail.com
Subject: Re: [Chicken-users] Segfaults with shared library, foreign code
Date: Mon, 28 Feb 2011 18:05:04 -0600
I've attached LD_DEBUG tails for all and libs as well as a gdb log,
though at this point I'm fairly sure this is a Clutter issue. What's strange
to
