[ltk-user] Getting up and running problem on W32 + sbcl
Hi. I have successfully gotten ltk's test programs and hello programs (from the manual) working on an MS Windows XP system using slime and clisp. On the same system, however, I am running into a problem with the Windows port of sbcl. I am not sure if this is expected or not, and I am at a loss about how to debug the problem, just getting started with it as I am. The debugger output from slime is below (with some Windows ^M linebreaks edited out). The wish shell does appear, and a graphical debugger window appears asking if I "wish to invoke the debugger" appears. Interestingly, if I set *break-on-signals* to t, the result is that it breaks earlier, telling me that there is no package :fly. I don't know if this is relevant... looking at the code it looks like it shouldn't be asking about that unless swank isn't loaded -- which it is. Anyway, perhaps the nature of the problem will be obvious to one of you. (lisp-implementation-version) => 1.0.37. It was 1.0.32, but I tried upgrading to the latest before asking here. Thanks for any pointers. --Evans (FORMATTER grid ~a -row ~a -column ~a~@[ -columnspan ~a~]~@[ -ipadx ~a~]~ ~@[ -ipady ~a~]~@[ -padx ~a~]~@[ -pady ~a~]~@[ -rowspan ~a~]~ ~@[ -sticky ~(~a~)~]) Compile-time error: (in macroexpansion of (FORMATTER "grid ~a -row ~a -column ~a~@[ -columnspan ~a~]~@[ -ipadx ~a~]~ ~@[ -ipady ~a~]~@[ -padx ~a~]~@[ -pady ~a~]~@[ -rowspan ~a~]~ ~@[ -sticky ~(~a~)~]")) (hint: For more precise location, try *BREAK-ON-SIGNALS*.) error in FORMAT: unknown directive (character: Return) grid ~a -row ~a -column ~a~@[ -columnspan ~a~]~@[ -ipadx ~a~]~ ~@[ -ipady ~a~]~@[ -padx ~a~]~@[ -pady ~a~]~@[ -rowspan ~a~]~ ~@[ -sticky ~(~a~)~] ^ [Condition of type SB-INT:COMPILED-PROGRAM-ERROR]
Hi Evans, while the error doesn't tell me much, you shouldn't get complaints about fly. As I am about to release a new ltk version, perhaps first try that one, you can find it at: http://ltk.rplay.net/svn/branches/ltk/repl/ltk.lisp and tell me about any problems you encounter with that version. Regards, Peter On Fri, May 21, 2010 at 8:11 AM, Evans H Winner III <thorne@unm.edu> wrote:
Hi. I have successfully gotten ltk's test programs and hello programs (from the manual) working on an MS Windows XP system using slime and clisp. On the same system, however, I am running into a problem with the Windows port of sbcl. I am not sure if this is expected or not, and I am at a loss about how to debug the problem, just getting started with it as I am. The debugger output from slime is below (with some Windows ^M linebreaks edited out). The wish shell does appear, and a graphical debugger window appears asking if I "wish to invoke the debugger" appears.
Interestingly, if I set *break-on-signals* to t, the result is that it breaks earlier, telling me that there is no package :fly. I don't know if this is relevant... looking at the code it looks like it shouldn't be asking about that unless swank isn't loaded -- which it is. Anyway, perhaps the nature of the problem will be obvious to one of you. (lisp-implementation-version) => 1.0.37. It was 1.0.32, but I tried upgrading to the latest before asking here. Thanks for any pointers. --Evans
(FORMATTER grid ~a -row ~a -column ~a~@[ -columnspan ~a~]~@[ -ipadx ~a~]~ ~@[ -ipady ~a~]~@[ -padx ~a~]~@[ -pady ~a~]~@[ -rowspan ~a~]~ ~@[ -sticky ~(~a~)~]) Compile-time error: (in macroexpansion of (FORMATTER "grid ~a -row ~a -column ~a~@[ -columnspan ~a~]~@[ -ipadx ~a~]~ ~@[ -ipady ~a~]~@[ -padx ~a~]~@[ -pady ~a~]~@[ -rowspan ~a~]~ ~@[ -sticky ~(~a~)~]")) (hint: For more precise location, try *BREAK-ON-SIGNALS*.) error in FORMAT: unknown directive (character: Return) grid ~a -row ~a -column ~a~@[ -columnspan ~a~]~@[ -ipadx ~a~]~ ~@[ -ipady ~a~]~@[ -padx ~a~]~@[ -pady ~a~]~@[ -rowspan ~a~]~ ~@[ -sticky ~(~a~)~]
^ [Condition of type SB-INT:COMPILED-PROGRAM-ERROR]
_______________________________________________ ltk-user site list ltk-user@common-lisp.net http://common-lisp.net/mailman/listinfo/ltk-user
On Fri, 21 May 2010 10:43:29 +0200 Peter Herth <herth@peter-herth.de> wrote:
Hi Evans,
while the error doesn't tell me much, you shouldn't get complaints about fly. As I am about to release a new ltk version, perhaps first try that one, you can find it at:
Thank you. I tried that file and got the same result. However, I realized that I had not tried it outside of slime, just using a command line. I find that when there are mysterious problems in Lisp, about 60% of the time if I take slime out of the equation then things magically work (and if they don't work, at least the debugger output is comprehensible). So the problem apparently is related to slime. I would be happy to take any actions to try to figure out what the problem is, but I have to admit that I wouldn't know where to start without some suggestions.
participants (2)
-
Evans H Winner III -
Peter Herth