From: Eli Zaretskii <eliz@gnu.org>
To: Andy Moreton <andrewjmoreton@gmail.com>
Cc: 43700@debbugs.gnu.org
Subject: bug#43700: 28.0.50; Crash creating a second frame
Date: Tue, 29 Sep 2020 17:37:40 +0300 [thread overview]
Message-ID: <83y2ksk5sb.fsf@gnu.org> (raw)
In-Reply-To: <d6dd33a4-4196-6de4-dfe4-09b3add83e72@gmail.com> (message from Andy Moreton on Tue, 29 Sep 2020 11:46:48 +0100)
> From: Andy Moreton <andrewjmoreton@gmail.com>
> Date: Tue, 29 Sep 2020 11:46:48 +0100
>
> After loading emacs (and files saved by desktop), do C-x 5 2 to create a
> new frame. Emacs crashes, and gdb shows the following backtrace.
Is this repeatable? Does it happen with "emacs -Q", per chance? Or
with unoptimized builds?
> This seems to have something to do with toolbars, but ~/.emacs.d/init.el
> contains "(tool-bar-mode 0)" so it shouldn't be doing anything with toolbars.
Creating a frame makes a keymap for the tool bar, whether it's
displayed or not.
But look at this part:
> #9 0x00000004001e76b1 in FACE_FROM_ID (id=0x162880, f=0x154e25ed5d860000) at
> C:/emacs/git/emacs/master/src/frame.h:1460
> No locals.
> #10 lookup_image (f=0x154e25ed5d860000, f@entry=0x6edbab0, spec=XIL(0),
> spec@entry=XIL(0xcd2b873), face_id=0x162880, face_id@entry=0xffffffff) at
> C:/emacs/git/emacs/master/src/image.c:2332
> img = <optimized out>
> hash = <optimized out>
> face = <optimized out>
> foreground = <optimized out>
> background = <optimized out>
> #11 0x00000004001e8235 in Fimage_mask_p (spec=XIL(0xcd2b873), frame=XIL(0)) at
> C:/emacs/git/emacs/master/src/image.c:1114
> f = 0x6edbab0
Look at the reasonable values of the arguments at entry to
lookup_image, and the garbled values at the crash site. The line that
calls FACE_FROM_ID is the first executable line of lookup_image, so
this could have happened only if the optimizations moved some
non-trivial code between the entry to the function and that line. Or
maybe something else is at work here.
next prev parent reply other threads:[~2020-09-29 14:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 10:46 bug#43700: 28.0.50; Crash creating a second frame Andy Moreton
2020-09-29 14:37 ` Eli Zaretskii [this message]
2020-09-29 14:49 ` Andy Moreton
2020-09-30 20:06 ` Andy Moreton
2020-10-01 0:15 ` Andy Moreton
2020-10-01 12:53 ` Eli Zaretskii
2020-10-02 0:38 ` Andy Moreton
2020-10-02 11:49 ` Eli Zaretskii
2020-10-02 23:07 ` Andy Moreton
2020-10-03 8:16 ` Eli Zaretskii
2020-10-03 12:26 ` Andy Moreton
2020-10-03 12:45 ` Eli Zaretskii
2020-10-03 13:40 ` Andy Moreton
2020-10-03 14:02 ` Eli Zaretskii
2020-10-03 14:05 ` Andy Moreton
2020-10-03 14:32 ` Eli Zaretskii
2020-10-03 17:03 ` Andy Moreton
2020-10-03 17:18 ` Eli Zaretskii
2020-10-03 17:21 ` Lars Ingebrigtsen
2020-10-03 17:54 ` Eli Zaretskii
2020-10-03 17:56 ` Lars Ingebrigtsen
2020-10-03 18:00 ` Eli Zaretskii
2020-10-03 18:21 ` Andy Moreton
2020-10-03 18:29 ` Eli Zaretskii
2020-10-03 17:51 ` Eli Zaretskii
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=83y2ksk5sb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=43700@debbugs.gnu.org \
--cc=andrewjmoreton@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).