[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Running until first unhandled error.

From: Davin Pearson
Subject: Running until first unhandled error.
Date: Wed, 4 Jan 2023 17:25:57 +1300

I am trying to get edebug online instead of checkpointing every
second line of code and in every buffer like so to narrow down
the source of the bug, i.e. an unhandled error message.

(message "&foo:100:")
(defun foo ()
  (message "&foo:101:")
  (setq abc 123)
  (message "&foo:102:")
  (message "&foo:103:")
  (message "&foo:104:")
  (setq def 456)
  (message "&foo:105:")
(message "&foo:106:")

I eval a buffer using


and it enters me into the *Debugger* as it should.

What I want to do is to run until the next unhandled error message,
but none of the *Debugger* keys seem to do this.  The Elisp
documentation is not very clear on this point.

Here are my edebug settings for you to help me debug
my code:

  (require 'debug)
  (require 'edebug)
  (setq edebug-all-defs t)
  (setq edebug-all-forms t)
  (setq edebug-on-error t)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]