Peter TB Brett <pe...@peter-b.co.uk> writes: > I've added a testsuite for the libgeda Scheme API. In one commit [2], > the testsuite succeeds. In the following commit [3], a test which does > not touch any of the changed code starts causing a segfault in the Guile > interpreter. > > [snip] > > Valgrind / Memcheck wasn't very helpful either. Is there a way to make > Guile zero each new heap page it requests before using it in order to > reduce the number of false positives the gc generates in Memcheck? > > In fact, *none* of the ways I've found of running the test without the > segfault occurring have given me *any* clue as to how to fix it > "properly". > > I'd really appreciate any suggestions that anyone might be able to give > me on figuring out how I've managed to break things. At the moment, I'm > at a complete loss.
So far, as far as I can tell the problem is due to freelist corruption
in the garbage collector, and I'm not sufficiently au fait with Guile
internals to be able to diagnose what's going on. Is this a known
issue?
Peter
--
Peter Brett <pe...@peter-b.co.uk>
Remote Sensing Research Group
Surrey Space Centre
pgpOMfYjTnTz8.pgp
Description: PGP signature
