GNU bug report logs - #66589
30.0.50; core dump in redisplay

Previous Next

Full log

View this message in rfc822 format

From: Evgeny Zajcev <lg.zevlg <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Florian Weimer <fweimer <at> redhat.com>, 66589 <at> debbugs.gnu.org
Subject: bug#66589: 30.0.50; core dump in redisplay
Date: Mon, 11 Mar 2024 18:32:44 +0300

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

пн, 11 мар. 2024 г. в 16:21, Eli Zaretskii <eliz <at> gnu.org>:

> > From: Florian Weimer <fweimer <at> redhat.com>
> > Cc: Evgeny Zajcev <lg.zevlg <at> gmail.com>,  66589 <at> debbugs.gnu.org
> > Date: Mon, 11 Mar 2024 11:26:00 +0100
> >
> > * Eli Zaretskii:
> >
> > > Very strange.  This means that both it->char_to_display and it->c are
> > > bogus, and I have no idea how this could happen.  So it is very
> > > important that you try to provide a reproduction recipe for this.  I
> > > will nevertheless try to see if I can figure out how such a situation
> > > could ever happen.
> >
> > For me, this (negative it->c value and subsequent fortify crash in
> > sprintf) happens when displaying an Arabic spam message.  This only
> > happens during article display.  Copying the message header and text
> > into a different buffer under text-mode Emacs and then opening it in
> > graphical Emacs does not trigger the crash for me.
>
> Thanks.  Any hope of a reproducible recipe, starting from "emacs -Q"
> (and taking into consideration that I don't use Gnus and know very
> little about it)?
>

Very hard to reproduce, since then I did not have any related crashes

-- 
lg

[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.