[slime-devel] [BUG] a repeatable way to crash a utf-8 slime session

[Harald Hanche-Olsen]

+ Samium Gromoff <_deepfire at feelingofgreen.ru>:

| While figuring out how to deal with unicode i stumbled upon across
| something which appeared to be killing slime session/sbcl with an ensuing
| emacs message telling something about process filters.
| 
| Urfin from #lisp helped me to narrow this down to evaluation of
| (format t "~c" #\UD0BB), or otherwise getting #\UD0BB shown on the screen,
| like having it displayed as the result of evaluation.
| 
| It seems to have a 100% repeatability.

Does it apply only to this magical value (which would be strange
indeed), or to any other character for which emacs cannot find a
glyph?

| I have yesterday's slime and sbcl 1.0/x86/Linux.

FWIW, I can't reproduce this with today's slime and
sbcl 1.0.1.33/ppc/MacOS X.


I don't use slime-net-coding-system, but instead have

(setf slime-lisp-implementations
      '((sbcl ("sbcl") :coding-system utf-8-unix)
	(cmucl ("cmucl") :coding-system iso-latin-1-unix)))

However I believe the effect should be the same, so this comment is
probably irrelevant.

- Harald