Karl> For the bug report I just sent, I included a stack dump generated by Karl> running gdb on the core file, then typing the "where full" command. Karl> There are strings in there that I believe are Lisp byte-code. Am I Karl> correct? How do I go about finding out which Lisp program that is? In general, it's difficult. and not generally useful. If you run under the debugger, `lbt' is the debugger command that gives you a lisp stacktrace. See src/.gdbinit. Karl> Perhaps knowing that would help lead to finding out what triggers a Karl> segv during gc_sweep()? It's more likely that bad gcpro happen in the C functions that get called. Lisp functions can't corrupt memory or cause gc problems without help from C.