Re: GC debugging tips?
Julian Bradfield writes:
>As you point out later, that's presumably a problem with
stack depth
>being exceeded. However, we'd like to know why VM or GC is using so
>much stack.
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.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta