[ab] problems with cocoahelper

[Luke Crook]

Brad Beveridge <brad.beveridge at ...> writes:

> > So, you can use it, but the Slime debugger is pretty broken.
> Hmm, thinking slightly deeper on this: SDL installs handlers for
> SIGTERM and SIGINT.  To cause a break Slime sends SIGINT (I think this
> is always true).  What does this mean for our SDL on Lisp app?
> So, this brings to mind the question - can anybody break their SDL app
> with Slime's C-c C-b combo?  If so, how the hell does this work?

SDL+SBCL+Slime in win32 seems to work as advertised when C-c C-b is pressed. 
SDL by default generates a quit interrupt when SIGTERM/SIGINT is received. So 
I'm guessing Slime generates SIGTERM/SIGINT which is caught by SDL which in 
turn generates a SDL_QuitEvent. So pressing C-c C-b causes the lispbuilder-sdl 
applications to exit cleanly.

Now C-c C-b when running lispbuilder-windows + lispbuilder-OpenRM kills the 
Lisp image dead. 

Documentation on this is difficult to find.

http://vogons.zetafleet.com/
viewtopic.php?t=15370&sid=56d888798c459985fe564a8d79d8c35c

- Luke