unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Davin Pearson <davin.pearson@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Running until first unhandled error.
Date: Wed, 4 Jan 2023 17:25:57 +1300	[thread overview]
Message-ID: <CAG9ihEuMHpAp3FWJGWbA6T6xmPB1LOgd8o9P3RP0wo5sav_WXw@mail.gmail.com> (raw)

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:")
  (foo)
  (message "&foo:103:")
  (bar)
  (message "&foo:104:")
  (setq def 456)
  (message "&foo:105:")
  )
(message "&foo:106:")

I eval a buffer using

(progn
  (mark-whole-buffer)
  (eval-buffer))

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:

(progn
  (require 'debug)
  (require 'edebug)
  (setq edebug-all-defs t)
  (setq edebug-all-forms t)
  (setq edebug-on-error t)
  (edebug-eval-top-level-form)
  )

*Davin.*


             reply	other threads:[~2023-01-04  4:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04  4:25 Davin Pearson [this message]
2023-01-04  8:53 ` Running until first unhandled error Jean Louis
2023-01-04 11:03 ` Michael Heerdegen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAG9ihEuMHpAp3FWJGWbA6T6xmPB1LOgd8o9P3RP0wo5sav_WXw@mail.gmail.com \
    --to=davin.pearson@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).