I have managed to track down the issue to these changes betwen two versions of swank-allegro.lisp
(defmethod debugger-info-for-emacs (start end) - (list (debugger-condition-for-emacs) + (list (format-condition-for-emacs) (format-restarts-for-emacs) (backtrace start end)))
(defmethod frame-locals (index) (let ((frame (nth-frame index))) (loop for i from 0 below (debugger:frame-number-vars frame) - collect (list :name (to-string (debugger:frame-var-name frame i)) + collect (list :symbol (debugger:frame-var-name frame i) :id 0 :value-string (to-string (debugger:frame-var-value frame i))))))
If i am not changing the file everything works perfectly yet after applying changes to the function frame-locals slime puts nil's instead of variable names.
And modifying debugger-info-for-emacs effectively disables the debuger ... Ignas Mikalajunas
I have managed to find the cause of the (debugger-info-for-emacs) failing. In documentation it is said: (debugger-info-for-emacs) returns a list (condition-description ...)
condition-description---a string describing the condition that triggered the debugger.
yet debugger-condition-for-emacs -
(defun debugger-condition-for-emacs () (list (safe-condition-message *swank-debugger-condition*) (format nil " [Condition of type ~S]" (type-of *swank-debugger-condition*))))
the function generating condition-description returns a list of two strings ... so it is pretty strange that I was the only one to encounter this problem ... Ignas Mikalajunas
Ignas Mikalajunas i.mikalajunas@mbt.lt writes:
I have managed to find the cause of the (debugger-info-for-emacs) failing. In documentation it is said:
The documentation is out of sync with the implementation. Will fix.
[...]
the function generating condition-description returns a list of two strings ... so it is pretty strange that I was the only one to encounter this problem ...
Very strange indeed. Are you sure you don't have a stale .elc file around?
Helmut.