[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs crash CVS 2003-10-17
From: |
Kenichi Handa |
Subject: |
Re: Emacs crash CVS 2003-10-17 |
Date: |
Tue, 11 Nov 2003 09:15:30 +0900 (JST) |
User-agent: |
SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/21.3 (sparc-sun-solaris2.6) MULE/5.0 (SAKAKI) |
In article <address@hidden>, Werner LEMBERG <address@hidden> writes:
>> > Program received signal SIGSEGV, Segmentation fault.
>> > 0x08077c43 in fill_glyph_string (s=0xbfffe424, face_id=26,
>> > start=6, end=79, overlaps_p=0) at xdisp.c:16730
>> > 16730 = FONT_INFO_FROM_ID (f, face->font_info_id);
>>
>> I'd like to know the result of these:
>> (gdb) p *face
>> (gdb) p *glyph
> (gdb) p *face
> Cannot access memory at address 0x0
> (gdb) p *glyph
> $5 = {
> charpos = 7,
[...]
> face_id = 26,
Hmmm, then somehow, the call of FACE_FROM_ID here:
L16697 face = FACE_FROM_ID (f, glyph->face_id);
returns NULL.
Please show the result of these:
(gdb) p *f->face_cache
(gdb) p *f->face_cache->faces_by_id[26]
By the way, xbacktrace shows that Emacs crashed while
calling message. I remember you are using a separate frame
for the minibuffer, so the message of what-cursor-position
is shown in the minibuffer-only frame, right?
---
Ken'ichi HANDA
address@hidden