unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: james@jojojames.com
Cc: 57267@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#57267: 28.1; emacs crashes when loading too many images
Date: Fri, 19 Aug 2022 09:18:25 +0200	[thread overview]
Message-ID: <m21qtcitvi.fsf@Mini.fritz.box> (raw)
In-Reply-To: <4B3965F5-E6E3-489A-BCA8-A292387A5AF9@jojojames.com> (james@jojojames.com's message of "Fri, 19 Aug 2022 02:01:13 -0400")

This could be heap corruption, I think.

Can you please build Emacs with ASAN?  Something like:

  git clean -xdf
  ./autogen.sh
  ./configure CFLAGS="-g -O0 -fsanitize=address -fno-omit-frame-pointer" \
              LDFLAGS="-fsanitize=address -fno-omit-frame-pointer"
  make

Everything above in the root of your Git worktree.

Then start Emacs like this:

  cd src
  lldb emacs
  run

and do what you did to make it crash.  If it's a heap corruption, and
ASAN can detect it, it will break into LLDB at that point.  Then please
print backtraces and so on, as Eli said.





  reply	other threads:[~2022-08-19  7:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18  0:38 bug#57267: 28.1; emacs crashes when loading too many images james
2022-08-18  6:30 ` Eli Zaretskii
2022-08-18 18:49   ` james
2022-08-18 19:03     ` Eli Zaretskii
2022-08-18 20:14       ` james
2022-08-19  5:55         ` Eli Zaretskii
2022-08-19  6:01           ` james
2022-08-19  7:18             ` Gerd Möllmann [this message]
2022-08-19  7:22               ` Gerd Möllmann
2022-08-19 14:18                 ` james
2022-08-20  6:34                   ` Gerd Möllmann
2022-08-20 16:23                     ` james
2022-08-20 16:29                       ` james
2022-08-21  5:42                         ` Gerd Möllmann
2022-08-21  5:30                       ` Gerd Möllmann
2022-08-21 21:21                         ` james
2022-08-23  5:09                           ` Gerd Möllmann

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=m21qtcitvi.fsf@Mini.fritz.box \
    --to=gerd.moellmann@gmail.com \
    --cc=57267@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=james@jojojames.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).