unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Evgeny Zajcev <lg.zevlg@gmail.com>, 66589@debbugs.gnu.org
Subject: bug#66589: 30.0.50; core dump in redisplay
Date: Mon, 11 Mar 2024 11:26:00 +0100	[thread overview]
Message-ID: <87frwxqd3b.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <83a5sgnop9.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 18 Oct 2023 14:40:34 +0300")

* 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,
Florian






  reply	other threads:[~2024-03-11 10:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-17  9:53 bug#66589: 30.0.50; core dump in redisplay Evgeny Zajcev
2023-10-17 11:29 ` Eli Zaretskii
2023-10-17 12:34   ` Gerd Möllmann
2023-10-17 13:36   ` Evgeny Zajcev
2023-10-17 15:01     ` Eli Zaretskii
2023-10-17 15:11       ` Evgeny Zajcev
2023-10-17 15:14         ` Evgeny Zajcev
2023-10-17 17:59         ` Eli Zaretskii
2023-10-17 18:11           ` Evgeny Zajcev
2023-10-17 19:23             ` Eli Zaretskii
2023-10-17 19:34               ` Evgeny Zajcev
2023-10-17 19:37                 ` Evgeny Zajcev
2023-10-18 11:40                   ` Eli Zaretskii
2024-03-11 10:26                     ` Florian Weimer [this message]
2024-03-11 13:21                       ` Eli Zaretskii
2024-03-11 15:32                         ` Evgeny Zajcev

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=87frwxqd3b.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=66589@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=lg.zevlg@gmail.com \
    /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).