From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Problems with debug-on-entry in the Lisp debugger.
Date: Mon, 07 Mar 2005 14:40:51 +0100 [thread overview]
Message-ID: <m365038tgc.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <87sm37n2bv.fsf@xs4all.nl> (Lute Kamstra's message of "Mon, 07 Mar 2005 12:05:24 +0100")
Lute Kamstra <Lute.Kamstra.lists@xs4all.nl> writes:
> 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.
You could define a bit in the Lisp_Symbol, like this:
struct Lisp_Symbol
{
unsigned gcmarkbit : 1;
/* Non-zero means symbol serves as a variable alias. The symbol
holding the real value is found in the value slot. */
unsigned indirect_variable : 1;
/* Non-zero means call debugger on entry. */
unsigned debug_on_entry;
...
};
Then you would define debug-on-entry and cancel-debug-on-entry
in C as well, which simply set or clear that bit.
next prev parent reply other threads:[~2005-03-07 13:40 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 [this message]
2005-03-07 14:20 ` drkm
2005-03-07 14:45 ` Kim F. Storm
2005-03-08 2:53 ` Richard Stallman
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
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=m365038tgc.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).