unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: bojohan+news@dd.chalmers.se (Johan Bockgård)
Subject: Re: Problems remaining in FOR-RELEASE
Date: Fri, 18 Mar 2005 14:16:09 +0100	[thread overview]
Message-ID: <yoijeked857q.fsf@hild.dd.chalmers.se> (raw)
In-Reply-To: m38y4l5lqd.fsf@kfs-l.imdomain.dk

storm@cua.dk (Kim F. Storm) writes:

> +-----------------------------------------------------
> | ** Investigate face cache related crash.
> |  
> | Indications: Face cache seems to have been cleared, but
> | redisplay uses an invalidated face_id with FACE_FROM_ID
> | which then returns a NULL pointer.  Said to happen with
> | isearch faces.
>
>
> I installed fixes related to this problem recently, and have not
> received any indications that the problem still exists. So if some
> of you still see the problem, please tell me.

I can still make it crash:

----------------------------------------------------------------

Using `C-x 3' in `emacs -nw -Q' after evaluating the following code
makes emacs crash:

(set-display-table-slot
 standard-display-table
 'vertical-border
 (let* ((face 'isearch)
        (face-offset (lsh (face-id face) 19)))
   (+ face-offset ?\|)))

----

(gdb) p face
$1 = (struct face *) 0x0
(gdb) bt
#0  turn_on_face (f=0x903710, face_id=27) at term.c:1911
#1  0x0000000000467d26 in write_glyphs (string=0x2a96c7f628, len=24)
    at term.c:965
#2  0x0000000000411db2 in update_frame_line (f=0x903710, vpos=0)
    at dispnew.c:5656
#3  0x0000000000410fab in update_frame_1 (f=0x903710, force_p=0, 
    inhibit_id_p=0) at dispnew.c:5154
#4  0x000000000040f297 in update_frame (f=0x903710, force_p=0, 
    inhibit_hairy_id_p=0) at dispnew.c:3853
#5  0x0000000000429484 in redisplay_internal (preserve_echo_area=9451280)
    at xdisp.c:10432
[...]

----------------------------------------------------------------

-- 
Johan Bockgård

      reply	other threads:[~2005-03-18 13:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-18  5:24 Problems remaining in FOR-RELEASE Richard Stallman
2005-03-18  9:47 ` Kim F. Storm
2005-03-18 13:16   ` Johan Bockgård [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=yoijeked857q.fsf@hild.dd.chalmers.se \
    --to=bojohan+news@dd.chalmers.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).