GNU bug report logs - #36312
27.0.50; (message) in display spec condition causes emacs_abort()

Previous Next

Package: emacs;

Reported by: Pip Cet <pipcet <at> gmail.com>

Date: Thu, 20 Jun 2019 16:19:02 UTC

Severity: normal

Found in version 27.0.50

Done: Pip Cet <pipcet <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Pip Cet <pipcet <at> gmail.com>
Cc: 36312 <at> debbugs.gnu.org
Subject: Re: bug#36312: 27.0.50;
 (message) in display spec condition causes emacs_abort()
Date: Thu, 20 Jun 2019 21:11:43 +0300
> From: Pip Cet <pipcet <at> gmail.com>
> Date: Thu, 20 Jun 2019 16:06:25 +0000
> 
> In emacs -Q, evaluate
> 
> (let ((o (make-overlay (point) (point))))
>   (overlay-put o 'after-string (propertize " " 'display
>                        '(when (message "a")
>   . "b"))))
> 
> This causes a SIGABRT in the bidi stack code.

Thanks.

You do realize that calling 'message' in a display-spec form causes us
to re-enter redisplay in the middle of redisplay?  I didn't even know
we allowed that, but there's something new about our display code to
learn every day.

Should be fixed now.

P.S. Is there a chance fontification-functions will also call
'message'?  Because I think we have the same problem there.




This bug report was last modified 6 years and 31 days ago.

Previous Next


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