[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Problems with debug-on-entry in the Lisp debugger.
From: |
Kim F. Storm |
Subject: |
Re: Problems with debug-on-entry in the Lisp debugger. |
Date: |
Mon, 07 Mar 2005 14:40:51 +0100 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) |
Lute Kamstra <address@hidden> 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.
Re: Problems with debug-on-entry in the Lisp debugger.,
Kim F. Storm <=
Re: Problems with debug-on-entry in the Lisp debugger., Richard Stallman, 2005/03/07
- Re: Problems with debug-on-entry in the Lisp debugger., Lute Kamstra, 2005/03/08
- Re: Problems with debug-on-entry in the Lisp debugger., Richard Stallman, 2005/03/09
- Re: Problems with debug-on-entry in the Lisp debugger., Richard Stallman, 2005/03/09
- Re: Problems with debug-on-entry in the Lisp debugger., Lute Kamstra, 2005/03/09
- Re: Problems with debug-on-entry in the Lisp debugger., Kevin Rodgers, 2005/03/09