2009/12/29 Luke J Crook <luke@...>:
> Because the library was not loaded the first path was taken. I think the crash
> is because the SDL process creates a new thread to handle the audio callback (a
> thread unbeknownst to the Lisp process). The unknown thread then performs the
> callback into Lisp and all hell seems to break loose.
This -- calling into lisp from non-lisp threads isn't supported in SBCL.
Not that it's impossible, just tricky. The right way to do this would
probably be to set up a temporary "virtual" lisp thread while the
callback is active if there is no real lisp thread corresponding to
the current native thread.