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: Fri, 02 Oct 2020 14:49:36 +0300 [thread overview]
Message-ID: <83d020g84v.fsf@gnu.org> (raw)
In-Reply-To: <14da5210-bba0-9e33-65dc-a76e7f3878fe@gmail.com> (message from Andy Moreton on Fri, 2 Oct 2020 01:38:25 +0100)
> Cc: 43700@debbugs.gnu.org
> From: Andy Moreton <andrewjmoreton@gmail.com>
> Date: Fri, 2 Oct 2020 01:38:25 +0100
>
> On 01/10/2020 13:53, Eli Zaretskii wrote:
> > If you put a breakpoint in lookup_image, on the line indicated below:
> >
> > ptrdiff_t
> > lookup_image (struct frame *f, Lisp_Object spec, int face_id)
> > {
> > struct image *img;
> > EMACS_UINT hash;
> >
> > struct face *face = (face_id >= 0) ? FACE_FROM_ID (f, face_id)
> > : FACE_FROM_ID (f, DEFAULT_FACE_ID);
> > unsigned long foreground = FACE_COLOR_TO_PIXEL (face->foreground, f); <<<<
> > unsigned long background = FACE_COLOR_TO_PIXEL (face->background, f);
> >
> > and condition the breakpoint by face == 0, does it break before the
> > crash when you perform the steps that reproduces the problem?
>
> Yes it does.
So the next question is: how come the default face is not available?
When that breakpoint breaks, what is the value of
FRAME_FACE_CACHE (f)->used
Is it zero, per chance? If so, I'd be interested to understand which
code resets the frame's face cache in this recipe.
> >> #11 0x00000004002c86e5 in lookup_image (f=0x5123410, spec=XIL(0xbc42793), face_id=0xffffffff) at C:/emacs/git/emacs/master/src/image.c:2334
> >
> > Why does face_id have the value 0xffffffff? The caller passes -1:
>
> This seems to be because I have "set output-radix 16" in ~/.gdbinit, so
> it displays the raw hex value. After "set output-radix 10" it displays
> the value as -1. Nothing untoward here.
Ah, okay. Nothing to worry about, then.
Thanks.
next prev parent reply other threads:[~2020-10-02 11:49 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
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 [this message]
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=83d020g84v.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).