On Wed, Mar 11, 2009 at 7:25 PM, Taylor Venable <tay...@metasyntax.net> wrote: > > Well I was able to trigger a hang in my build with the debugging > symbols by setting the nursery stack size to 10k. Debug log from GDB > is attached. The three entries here were taken from allowing the > program to run for varying periods of time. The behaviour I got > spiked the CPU but the memory usage did not increase visibly. Hope > this sheds a little more light; if not let me know and I can go back > at it. (I notice here that the proc parameter to C_reclaim is the > null pointer, don't know if that's meaningful or not...)
The proc being 0 is ok. Apparently the GC looping: it might be that some sort of stack-limit check is constantly failing which results in one GC after the other. It would be cool, if you could step out of the GC (reclaim) and follow the execution - does it trigger a new GC right away? cheers, felix _______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
