Re: Valgrind fix

2010-04-13 Thread Ludovic Courtès
Hi! No Itisnt writes: > Boehm GC CVS now has a patch that will fix this behavior. Compile with > threads and -DUSE_GET_STACKBASE_FOR_MAIN. See the following thread for > details. > > http://comments.gmane.org/gmane.comp.programming.garbage-collection.boehmgc/3788 > > If Hans Boehm agrees, the be

Re: Valgrind fix

2010-03-12 Thread No Itisnt
Boehm GC CVS now has a patch that will fix this behavior. Compile with threads and -DUSE_GET_STACKBASE_FOR_MAIN. See the following thread for details. http://comments.gmane.org/gmane.comp.programming.garbage-collection.boehmgc/3788 If Hans Boehm agrees, the behavior will probably become default a

Re: Valgrind fix

2010-03-08 Thread Ludovic Courtès
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

Re: Valgrind fix

2010-03-08 Thread Ludovic Courtès
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

RE: Valgrind fix

2010-03-08 Thread No Itisnt
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

Valgrind fix

2010-03-07 Thread No Itisnt
Here is patch that allows valgrind to run Guile under Linux non-IA64 architectures. It also fixes a potential leak in threads.c where a pthread attribute was not destroyed. Note that libgc still generates lots of warnings. For now, I've just been suppressing all warnings from libgc, and I'm happy

Valgrind fix

2010-03-07 Thread No Itisnt
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. Note that libgc still generates lots of warnings. For now, I've just been suppressing all warnings from libgc, and I'm happy to rep