From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: pegzmasta@member.fsf.org, 35725@debbugs.gnu.org
Subject: bug#35725: 26.2; Fatal error 11: Segmentation fault; Crash on: (find-file "any.svg")
Date: Tue, 14 May 2019 18:25:34 +0300 [thread overview]
Message-ID: <83k1et9hxt.fsf@gnu.org> (raw)
In-Reply-To: <87sgthg7i8.fsf@gmail.com> (message from Noam Postavsky on Mon, 13 May 2019 21:16:47 -0400)
> From: Noam Postavsky <npostavs@gmail.com>
> Date: Mon, 13 May 2019 21:16:47 -0400
> Cc: 35725@debbugs.gnu.org
>
> I think this might be the same as Bug#29581; we closed that as being a
> bug in some version of ImageMagick, but it's occurring to me that since
> the backtrace ends in emacs, perhaps it is actually an Emacs bug after
> all.
What ends in Emacs is that our fatal signal handler is called, and
tries to handle the segfault. But the segfault itself is clearly
inside ImageMagick, not in Emacs code. Which still might mean we
somehow cause it, but I think we will need an ImageMagick expert, or
at least someone who will step through ImageMagick code, to tell us
what exactly is wrong, and why.
prev parent reply other threads:[~2019-05-14 15:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 22:40 bug#35725: 26.2; Fatal error 11: Segmentation fault; Crash on: (find-file "any.svg") Michael Pagan
2019-05-14 1:04 ` Paul Eggert
2019-05-14 1:21 ` Glenn Morris
2019-05-14 3:59 ` Michael Pagan
2019-05-14 7:58 ` Lars Ingebrigtsen
2019-05-14 8:00 ` Lars Ingebrigtsen
2019-05-14 16:04 ` Eli Zaretskii
2019-05-14 16:16 ` Paul Eggert
2019-05-15 0:49 ` Lars Ingebrigtsen
2019-05-15 18:45 ` Alan Third
2019-05-16 3:47 ` Lars Ingebrigtsen
2019-05-14 6:08 ` Paul Eggert
2019-05-15 0:42 ` Glenn Morris
2019-05-18 17:12 ` Paul Eggert
2019-05-15 4:07 ` Michael Pagan
2019-05-15 4:22 ` Lars Ingebrigtsen
2019-05-14 1:16 ` Noam Postavsky
2019-05-14 15:25 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83k1et9hxt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35725@debbugs.gnu.org \
--cc=npostavs@gmail.com \
--cc=pegzmasta@member.fsf.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.