Here's a program that demonstrates the actual issue at hand.
Basically, libgc finds the stack address from either glibc or the
kernel, which is not what it wants because valgrind messes with the
address space of the host program. This is only on Linux, but I
understand the issue is similar on other
Hi,
No Itisnt writes:
> Here is patch that allows valgrind to run Guile under Linux non-IA64
> systems. It also fixes a potential leak in threads.c where a
> pthread attribute was not destroyed.
Excellent, thanks! (For the record, the inability to use Valgrind with
libgc has been bothering us
Hi again,
I should’ve read this message before. Thanks for the explanation.
No Itisnt writes:
> The attached program grabs the stack address from the kernel, glibc,
> and by taking the address of a stack object, then prints the
> difference. When run normally, the differences are minimal, but
I want to apply for GSOC this year. Since Guile has recently obtained
a compilation/language framework, I was thinking that an
implementation of the Lua language for Guile, under the auspices of
the GNU Project, would be a good fit.
A little background on Lua: It has a reputation as an "extensible
