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

From: Chong Yidong <[email-masked]>
Date: Sun, 25 Nov 2012 13:30:46 +0800

Jan Djärv <[email-masked]> writes:

>> 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?

Yep.  Thanks for finding and fixing the bug.

Eli Zaretskii <[email-masked]> writes:

> Indeed, it they should.
>
> How did the code arrive at internal-char-font in this case?  The
> backtrace indicates it was from Lisp, so can you post a Lisp
> backtrace?

See below.  I'm not sure why describe-char-padded-string needs
internal-char-font for, though.

"internal-char-font" (0xffffafa0)
"if" (0xffffb238)
"describe-char-padded-string" (0xffffb478)
"mapconcat" (0xffffb640)
"concat" (0xffffb8b8)
"setcar" (0xffffba38)
"if" (0xffffbc08)
"if" (0xffffbe28)
"let" (0xffffc0e8)
"catch" (0xffffc458)
"or" (0xffffc628)
"progn" (0xffffc7f8)
"if" (0xffffc9c8)
"let*" (0xffffcc58)
"let" (0xffffcf08)
"describe-char" (0xffffd120)
"what-cursor-position" (0xffffd698)
"call-interactively" (0xffffd9b8)