[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Crash with edebug of turn-on-font-lock-if-enabled
From: |
Klaus Zeitler |
Subject: |
Re: Crash with edebug of turn-on-font-lock-if-enabled |
Date: |
Tue, 05 Jul 2005 16:06:31 +0200 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (usg-unix-v) |
>>>>> "Richard" == Richard M Stallman <address@hidden> writes:
Richard>
Richard> 1. emacs -Q&
Richard> 2. M-x global-font-lock-mode
Richard> 3. in scratch buffer eval: (minibuffer-electric-default-mode 1)
Richard> 4. C-x C-f <lisp-dir>/font-core.el
Richard> 5. search defun turn-on-font-lock-if-enabled
Richard> 6. instrument this function for edebug (C-u C-M-x)
Richard> 7. load a file .e.g. ~/x.sh (with a few continues in edebug)
Richard> 8. try to kill this buffer, i.e. C-x C-k
Richard>
Richard> Can you use a debugger to step thru Fkill_buffer
Richard> and its subroutines, and see why it crashes?
Looks like it's a recursion problem, I can also try other commands as step 8
above (like e.g. C-x b). Xbacktrace then gives me an endless trace like:
(gdb) Xbacktrace
0x4f45a5 Lisp type 5
"edebug-enter"
"edebug-enter"
"turn-on-font-lock"
"turn-on-font-lock-if-enabled"
"global-font-lock-mode-enable-in-buffers"
"global-font-lock-mode-check-buffers"
"run-hooks"
"recursive-edit"
"edebug-recursive-edit"
"edebug-display"
"edebug-debugger"
"edebug-before"
"edebug-after"
0x4f45a5 Lisp type 5
"edebug-enter"
"edebug-enter"
"turn-on-font-lock"
"turn-on-font-lock-if-enabled"
"global-font-lock-mode-enable-in-buffers"
"global-font-lock-mode-check-buffers"
"run-hooks"
"recursive-edit"
"edebug-recursive-edit"
"edebug-display"
"edebug-debugger"
"edebug-before"
"edebug-after"
0x4f45a5 Lisp type 5
---Type <return> to continue, or q <return> to quit---
"edebug-enter"
"edebug-enter"
"turn-on-font-lock"
"turn-on-font-lock-if-enabled"
"global-font-lock-mode-enable-in-buffers"
"global-font-lock-mode-check-buffers"
"run-hooks"
"recursive-edit"
"edebug-recursive-edit"
"edebug-display"
"edebug-debugger"
"edebug-before"
"edebug-after"
0x4f45a5 Lisp type 5
"edebug-enter"
"edebug-enter"
"turn-on-font-lock"
"turn-on-font-lock-if-enabled"
"global-font-lock-mode-enable-in-buffers"
"global-font-lock-mode-check-buffers"
"run-hooks"
"recursive-edit"
"edebug-recursive-edit"
"edebug-display"
"edebug-debugger"
"edebug-before"
"edebug-after"
0x4f45a5 Lisp type 5
"edebug-enter"
---Type <return> to continue, or q <return> to quit---
"edebug-enter"
"turn-on-font-lock"
"turn-on-font-lock-if-enabled"
"global-font-lock-mode-enable-in-buffers"
"global-font-lock-mode-check-buffers"
"run-hooks"
"recursive-edit"
"edebug-recursive-edit"
"edebug-display"
"edebug-debugger"
"edebug-before"
"edebug-after"
0x4f45a5 Lisp type 5
"edebug-enter"
"edebug-enter"
"turn-on-font-lock"
"turn-on-font-lock-if-enabled"
"global-font-lock-mode-enable-in-buffers"
...
--
------------------------------------------
| Klaus Zeitler Lucent Technologies |
| Email: address@hidden |
------------------------------------------
---
Life is what happens during long compiles.