GNU bug report logs - #12745
crash in bidi_pop_it during (idle) redisplay

Previous Next

Full log

Message #35 received at 12745 <at> debbugs.gnu.org (full text, mbox):

From: Ami Fischman <ami <at> fischman.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 12745 <at> debbugs.gnu.org
Subject: Re: bug#12745: crash in bidi_pop_it during (idle) redisplay
Date: Mon, 29 Oct 2012 11:29:28 -0700

[Message part 1 (text/plain, inline)]

On Mon, Oct 29, 2012 at 11:10 AM, Eli Zaretskii <eliz <at> gnu.org> wrote:

> Yes, and so is the STRETCH glyph.  Can you figure out what is the
> string before that, viz.:
> >  20  144: CHAR[ ] str=61334f1[0] blev=0,btyp=L w=6 a+d=10+2 MB
> This is a display string or an overlay string, but where does it come
> from, and which mode puts it there?
>

I'm groping in the dark, but AFAICT it's a null str?
(gdb) p/x (it->glyph_row->glyphs[1][20].object)
$39 = 0x61334f1
(gdb) p *(it->glyph_row->glyphs[1][20].object)
$40 = 0
I'm probably Doing It Wrong (tm), though.

The only guess I have is that I had entered a trailing space after that
comma, which would highlight it as trailing whitespace because of this
snippet from my .emacs:
(highlight-regexp "[ \t]+$" 'hi-blue)
using hi-lock-mode.

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.