Re: [Emacs-diffs] trunk r117741: Handle C stack overflow caused by too nested Lisp evaluation.

[Stefan Monnier]

> +  DEFVAR_LISP ("top-level-message", Vtop_level_message,
> +            doc: /* Message displayed by `normal-top-level'.  */);

Why does this need to be exported to Elisp?

> +  /* Hard GC error may lead to stack overflow caused by
> +     too nested calls to mark_object.  No way to survive.  */

I don't see why there's no way to survive.  Isn't it safe to interrupt
GC within the mark phase and re-run it?


        Stefan