bug#11964: describe-char causes a fatal error (abort trap: 6) in non-windowed mode

[Jan Djärv]

Hello.

This has been fixed in the trunk.
The problem was that ns-win created fontsets unconditionally during load and 
that lead to problems when running with -nw, in face_for_char.  Shouldn't 
fontsets/font objects be ignored if the terminal is a non-GUI one?

        Jan D.

23 nov 2012 kl. 08:07 skrev Jan Djärv <jan.h.d@swipnet.se>:

> Hello.
> 
> 23 nov 2012 kl. 07:26 skrev Chong Yidong <cyd@gnu.org>:
> 
>> Jan Djärv <jan.h.d@swipnet.se> writes:
>> 
>>> Here is a backtrace.  The fontdriver does not have an encode_char
>>> function (it is NULL).  But I don't know which driver this is.  Lisp
>>> backtrace is broken it seems.
>> 
>> Could you do
>> 
>> f 1
>> pp face->font->driver->type
>> 
>> and see what font driver it is (or if there is one)?
> 
> Basically no, because
> 
> p face->font->driver
> $3 = (struct font_driver *) 0x3
> 
> Uninitialized memory?
> 
>       Jan D.
>