"Steven E. Harris" seh@panix.com writes:
Luke Gorrie luke@synap.se writes:
Is it possible to SIGINT the lisp process in cygwin? With the unix build of CLISP that puts it into the debugger so you can see a backtrace of where it's stuck.
The stack trace isn't all to informative, but this warning from *inferior-lisp* may be:
,---- | ;; Connection to Emacs lost. | ;; [READ from #<INPUT STRING-INPUT-STREAM>: #<PACKAGE SWANK> has no external symbol with name "TOGGLE-TRACE-FDEFINITION"] `----
Actually, I think I just found the problem. I had not reloaded the updated slime.el into my long-running XEmacs instance. Upon reload, tracing works as expected.
Actually this is a useful reminder that we should handle protocol errors more gracefully. This case of the connection breaking if Emacs sends a message that is not understood makes it hard if you want to develop SLIME add-ons - you end up killing your connection if you try to call your Lisp code but forgot to load it first.
Onto the todo list for now.