emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Emacs crash CVS 2003-10-17


From: Werner LEMBERG
Subject: Re: Emacs crash CVS 2003-10-17
Date: Tue, 11 Nov 2003 06:29:04 +0100 (CET)

From: Kenichi Handa <address@hidden>
Subject: Re: Emacs crash CVS 2003-10-17
Date: Tue, 11 Nov 2003 09:15:30 +0900 (JST)

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

  (gdb) p *f->face_cache
  $6 = {
    buckets = 0x8660de0, 
    f = 0x85af0c0, 
    faces_by_id = 0x8ba02f0, 
    size = 200, 
    used = 21, 
    menu_face_changed_p = 0
  }
  (gdb) p *f->face_cache->faces_by_id[26]
  Cannot access memory at address 0x0

The last non-zero index is 20:

  (gdb) p *f->face_cache->faces_by_id[20]
  $19 = {
    id = 20, 
    gc = 0x8db55a8, 
    font = 0x8d63470, 
    stipple = 0, 
    foreground = 3355443, 
    background = 15066597, 
    underline_color = 0, 
    overline_color = 0, 
    strike_through_color = 0, 
    box_color = 12566463, 
    font_name = 0x8c94c38 
"-Etl-Fixed-Bold-R-Normal--24-240-72-72-C-120-ISO8859-1", 
    font_info_id = 0, 
    fontset = 22, 
    pixmap_w = 0, 
    pixmap_h = 0, 
    box_line_width = -1, 
    box = FACE_SIMPLE_BOX, 
    use_box_color_for_shadows_p = 1, 
    lface = {675056940, 1758776380, 675105332, 174, 675105476, 675105332, 
      675056556, 675056556, 1749329204, 1749332324, 675056556, 675056556, 
      675056556, -1471922728, 675056556, 675056556, 120}, 
    hash = 675090362, 
    charset = 0, 
    underline_p = 0, 
    overline_p = 0, 
    strike_through_p = 0, 
    foreground_defaulted_p = 0, 
    background_defaulted_p = 0, 
    underline_defaulted_p = 0, 
    overline_color_defaulted_p = 0, 
    strike_through_color_defaulted_p = 0, 
    box_color_defaulted_p = 1, 
    tty_bold_p = 0, 
    tty_dim_p = 0, 
    tty_underline_p = 0, 
    tty_alt_charset_p = 0, 
    tty_reverse_p = 0, 
    tty_blinking_p = 0, 
    colors_copied_bitwise_p = 0, 
    overstrike = 0, 
    next = 0x0, 
    prev = 0x0, 
    ascii_face = 0x8fb51c8
  }

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

No.  I only use a separate minibuffer-only frame if I access the
40x40 bitmap fonts for CNS-11643 which isn't the case currently.


    Werner




reply via email to

[Prev in Thread] Current Thread [Next in Thread]