Re: wrong-type-argument charsetp unbound error in emacs-unicode-2 current

[Bob Halley <halley@play-bow.org>]

James Cloos wrote:
>
> Which toolkit do you use?  I've noticed that using gtk (as emacs'
> toolkit) often leads to more bugs than the alternatives.....
>   
I configured emacs with --prefix=/usr/local/emacs-23 --with-gtk 
--enable-font-backend.

I've found out a few more things:

The elisp error can be triggered by evaluating (utf-8-string-p "foo").

Reverting to version 1.20.2.7 of select.el makes the lisp error go away 
and emacs no longer segfaults.  The difference between 1.20.2.7 and 
1.20.2.8 is the addition of utf-8-string-p and its associated ccl program.

To me, the evidence so far points at a problem in the ccl code.  I also 
think it is likely that whatever is broken is also smashing memory, as 
emacs stopped segfaulting when I reverted select.el.

I'll keep poking around and see if I can learn anything else.

/Bob