Re: my crash, the ultimate cause.

dv> Under gdb, I got in compiled_function_documentation[1], with a dv> doc_and_interactive field that was visibly corrupted (pobj would fail on it). dv> I don't think I've changed anything from then, but the next compilation worked dv> again .... As you said, the hunt is probably ot over ;-) It might be worthwhile to keep a build that fails, as long as it has debug information. The key help you get from gdb is hardware watchpoints. I had to do something like (gdb) watch *(int*) 0x838b938 Hardware watchpoint 2: *(int *) 137935160 to track changes to the word at address 0x838b938. Make sure gdb responds with `Hardware watchpoint'. dv> Footnotes: dv> [1] BTW, how can I know the name of such a function from the dv> Lisp_Compiled_Function struct ? Lisp functions don't have names!! This is why (lambda (foo) (bar foo)) can be compiled into a Lisp_Compiled_Function object. Look for a Ffuncall further up the backtrace, and do something like a pobj on its args[0] (untested). Martin