GC debugging tips?

Julian Bradfield writes: I regularly do that. So it's not just size, but size (I would guess) plus something folder-specific. 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. If you don't get a Lisp backtrace, or you don't trust the one you're seeing, try $ gdb xemacs (gdb) run # provoke crash (gdb) source xemacs-sources/src/.gdbinit # if you aren't in src/ (gdb) lbt That should tell us what VM was up to at the time. It's possible that GC has its shorts in a (Moebius) knot; do the last few of those stack frames seem to be going in circles? _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta