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

From: Chong Yidong <[email-masked]>
Date: Fri, 23 Nov 2012 17:28:14 +0800

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

> Basically no, because
>
> p face->font->driver
> $3 = (struct font_driver *) 0x3
>
> Uninitialized memory?

Yeah.

Could you try to debug this by stepping through face_for_char when it is
called via Finternal_char_font?  You should be able to do this by doing

b Finternal_char_font
r
[Do the recipe]
b face_for_char
c

Then, when the debugger hits the face_for_char breakpoint, step through
that function.  When the variables rfont_def and font_object get
assigned values, use pp to view their contents and see if they are
valid.

Thanks.