From: Alain P. <Dr....@gm...> - 2009-09-27 00:45:24
|
G'day! I'm starting a new personal project, having used Lispworks for many years, and SBCL seems to be "the open source lisp of choice", right now. Great work guys! Now to the bad news... :-) I have a (multi-threaded) application, which I start like this: % sbcl --core myapp.core --eval "(mypackage:start)" Once in a blue moon, I experienced something rather odd; the threads meant to be launched by START haven't even been run yet, and the console is left, frozen, in a debugger, with a stack like this one: (READ-CHAR #<SB-SYS:FD-STREAM for "the terminal" {D283941}> NIL #:EOF-OBJECT #<unused argument>) 5[6] u (SB-IMPL::INPUT-CHAR/UTF-8 #<SB-SYS:FD-STREAM for "the terminal" {D283941}> NIL #:EOF-OBJECT) 4[6] u (SB-IMPL::REFILL-INPUT-BUFFER #<SB-SYS:FD-STREAM for "the terminal" {D283941}>) 3[6] u (SB-SYS:WAIT-UNTIL-FD-USABLE 15 :INPUT NIL) 2[6] u (SB-SYS:DECODE-TIMEOUT NIL) 1[6] u (GET-INTERNAL-REAL-TIME) 0[6] u Top of stack. 0[6] Seems rather odd. The whole thing is started from `screen' when the machine boots. This was on sbcl 1.0.29. Haven't seen it since, but then again, I don't boot this machine terribly often ;-) Any clues will be welcome. Thanks! --Alain Picard -- Please read about why Top Posting is evil at: http://en.wikipedia.org/wiki/Top-posting and http://www.dickalba.demon.co.uk/usenet/guide/faq_topp.html Please read about why HTML in email is evil at: http://www.birdhouse.org/etc/evilmail.html |