Re: debugging post command hook max-lisp-eval-depth

[Stefan Monnier <monnier@iro.umontreal.ca>]

> every now and then my Emacs will get in a bad state because of some
> infinite recursion in the post-command-hook. I am reaching out for ideas
> on how to debug Emacs when it gets into this weird state. Keep in mind
> that it is hard to do anything with Emacs at that point since any
> command (switching buffer, starting debugger) will fail with the same
> error `Lisp nesting exceeds...'.

Hmm... post-command-hook is run via `safe_run_hooks` which is supposed
to try and catch errors such that when an error is caught the
corresponding function is removed from post-command-hook.

Of course, this is a just a mitigating factor, but it should prevent the
problem you describe, except in those cases where the offending function
is constantly re-added (e.g. by a pre-command-hook).

Another approach is something like:

    (advice-add 'debug :around
      (lambda (&rest args)
        (let ((post-command-hook nil))
          (apply args))))


-- Stefan