From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Problems with debug-on-entry in the Lisp debugger.
Date: Mon, 07 Mar 2005 21:53:03 -0500 [thread overview]
Message-ID: <E1D8UqF-0008L2-76@fencepost.gnu.org> (raw)
In-Reply-To: <87sm37n2bv.fsf@xs4all.nl> (message from Lute Kamstra on Mon, 07 Mar 2005 12:05:24 +0100)
The only solution (within the current implementation) that I can
think of, is to temporarily remove all debug-on-entry code while
stepping with `d'.
Would setting inhibit-debug-on-entry temporarily do the job?
I can think of two points in a macro to set a break for the
debugger: just before macro expansion and just after it, right
before the evaluation of the resulting sexp.
The correct place to do it is before macro expansion.
This is a very evident bug, so please just fix it if you can.
In both cases, hiding
the debug-on-entry code from the user of the debugger seems not
possible.
I am not sure what that means.
When I was thinking about these three problems, it seemed to me that
the easiest and simplest thing to do, is to move support for
debug-on-entry into the C implementation of the Lisp interpreter. To
mark a function for debug-on-entry, you could set the debug-on-entry
property of the function's symbol and the Lisp interpreter would then
call the debugger.
I agree this is undesirable due to slowness.
I don't see a need for this big a change.
next prev parent reply other threads:[~2005-03-08 2:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 11:05 Problems with debug-on-entry in the Lisp debugger Lute Kamstra
2005-03-07 13:31 ` Stefan Monnier
2005-03-07 15:20 ` Lute Kamstra
2005-03-07 16:32 ` Stefan Monnier
2005-03-08 18:57 ` Lute Kamstra
2005-03-09 16:58 ` Richard Stallman
2005-03-09 17:30 ` Lute Kamstra
2005-03-07 13:40 ` Kim F. Storm
2005-03-07 14:20 ` drkm
2005-03-07 14:45 ` Kim F. Storm
2005-03-08 2:53 ` Richard Stallman [this message]
2005-03-08 18:02 ` Lute Kamstra
2005-03-08 18:59 ` Stefan Monnier
2005-03-09 10:14 ` Lute Kamstra
2005-03-09 16:58 ` Richard Stallman
2005-03-09 16:58 ` Richard Stallman
2005-03-09 17:38 ` Lute Kamstra
2005-03-10 0:26 ` Kevin Rodgers
2005-03-11 1:47 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1D8UqF-0008L2-76@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.