13 Jan
2004
13 Jan
'04
10:28 a.m.
i'm in the process of porting the new backend to openmcl and i've managed to get emacs to block every single time i try to connect to slime. so far i've localized the problem to something inside slime-init-connection, but since emacs is blocked i can't get any debugging info (like the contents of stlime-events or access to inferior-lisp). whats the best way to go about debugging lime?
-- Marco Ring the bells that still can ring. Forget the perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen