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. In a VM folder with 30k messages, it doesn't surprise me that the Lisp object graph might contain paths 300k long. (I guess that GC explores depth-first rather than breadth-first?) If I remove the default limit (8MB on my laptop) on stack size, the problem goes away, so there's no infinite recursion going on. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta