Re: GC debugging tips?

> As I said, I compiled without any optimization (because optimized code > is too hard to debug for the kind of simple basic error one makes when > doing first-cut code!). So in particular there's no tail recursion > optimization, which GC relies upon to avoid stack blow-up in normal > life. Ah, OK, I didn't know that. Thanks for the explanation. So I guess we're cool with this ... maybe we should put something in the FAQ. For GCC at least there's probably an option to specify that optimization.