From: Stefan Kangas <stefan@marxist.se>
To: Sam Steingold <sds@gnu.org>
Cc: Alan Third <alan@idiocy.org>, 38723-done@debbugs.gnu.org
Subject: bug#38723: 27.0.50; macosx: [bootstrap-emacs.pdmp] Segmentation fault with ImageMagick
Date: Thu, 1 Oct 2020 05:50:42 -0700 [thread overview]
Message-ID: <CADwFkmmAMYq79j3a12WWZ90mBvpAyxeskY3LyA6QCKP8zkj-TQ@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmkswirZQ=Z1ZONUBSgvwxbEG9godc+VzUj=zKwUxgk2Wg@mail.gmail.com> (Stefan Kangas's message of "Tue, 25 Aug 2020 15:58:00 -0700")
Stefan Kangas <stefan@marxist.se> writes:
> Sam Steingold <sds@gnu.org> writes:
>
>>> * Alan Third <nyna@vqvbpl.bet> [2019-12-23 21:26:49 +0000]:
>>>
>>> On Mon, Dec 23, 2019 at 10:54:53AM -0500, Sam Steingold wrote:
>>>> (lldb) run --batch -l loadup --temacs=pbootstrap
>>> <snip>
>>>> Loading /Users/sam.steingold/src/emacs/trunk/lisp/image.el (source)...
>>>> Process 60246 stopped
>>>> * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x8)
>>>> frame #0: 0x0000000100eebddc libomp.dylib`__kmp_set_indirect_lock(unsigned int*, int) + 14
>>>> libomp.dylib`__kmp_set_indirect_lock:
>>>> -> 0x100eebddc <+14>: movl 0x8(%rax), %edx
>>>> 0x100eebddf <+17>: movq (%rcx,%rdx,8), %rcx
>>>> 0x100eebde3 <+21>: movq (%rax), %rdi
>>>> 0x100eebde6 <+24>: popq %rbp
>>>> Target 0: (temacs) stopped.
>>>> (lldb) bt
>>>> * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x8)
>>>> * frame #0: 0x0000000100eebddc libomp.dylib`__kmp_set_indirect_lock(unsigned int*, int) + 14
>>>> frame #1: 0x0000000100ebfd10 libomp.dylib`__kmpc_set_lock + 189
>>>> frame #2: 0x0000000100a8e835 libMagickCore-7.Q16HDRI.7.dylib`ActivateSemaphoreInfo + 39
>>>> frame #3: 0x0000000100a1aa7e libMagickCore-7.Q16HDRI.7.dylib`GetMagickInfo + 58
>>>> frame #4: 0x0000000100a1aed9 libMagickCore-7.Q16HDRI.7.dylib`GetMagickList + 104
>>>> frame #5: 0x00000001001c44e2 temacs`Fimagemagick_types at image.c:9294:13 [opt]
>>>> frame #6: 0x0000000100146b64 temacs`eval_sub(form=<unavailable>) at eval.c:2270:15 [opt]
>
> If I'm not mistaken, the crash here is within ImageMagick? In other
> words, this is not a bug in Emacs?
No further comments within 5 weeks. I'll therefore assume that the
above reasoning is correct, and I'm closing this bug now.
If the conclusion is incorrect and this is indeed an issue in Emacs,
please reply to this email (use "Reply to all" in your email client) and
we can reopen the bug report.
prev parent reply other threads:[~2020-10-01 12:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 15:54 bug#38723: 27.0.50; macosx: [bootstrap-emacs.pdmp] Segmentation fault with ImageMagick Sam Steingold
2019-12-23 21:26 ` Alan Third
2019-12-23 21:45 ` Sam Steingold
2020-08-25 22:58 ` Stefan Kangas
2020-10-01 12:50 ` Stefan Kangas [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
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=CADwFkmmAMYq79j3a12WWZ90mBvpAyxeskY3LyA6QCKP8zkj-TQ@mail.gmail.com \
--to=stefan@marxist.se \
--cc=38723-done@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=sds@gnu.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 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).