From: Andy Moreton <andrewjmoreton@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 43700@debbugs.gnu.org
Subject: bug#43700: 28.0.50; Crash creating a second frame
Date: Sat, 3 Oct 2020 13:26:09 +0100 [thread overview]
Message-ID: <572e3be7-6f96-90f3-192d-fa0b51f85218@gmail.com> (raw)
In-Reply-To: <83362vhgh9.fsf@gnu.org>
On 03/10/2020 09:16, Eli Zaretskii wrote:
> OK. x-create-frame in w32fns.c initializes the basic faces of the
> frame, here:
>
> /* Init faces first since we need the frame's column width/line
> height in various occasions. */
> init_frame_faces (f);
>
> I suggest to put a breakpoint after that function returns, and when it
> breaks for the second frame you are creating, put a watchpoint on the
> frame's face cache, like this:
>
> (gdb) watch -l f->face_cache->used if f->face_cache->used == 0
>
> Then produce a backtrace from any time this watchpoint fires. That
> should show us the culprit.
The watchpoint does not fire before the segfault, so there is clearly
something wrong with gdb on this platform :-(
AndyM
next prev parent reply other threads:[~2020-10-03 12:26 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
2020-10-02 23:07 ` Andy Moreton
2020-10-03 8:16 ` Eli Zaretskii
2020-10-03 12:26 ` Andy Moreton [this message]
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=572e3be7-6f96-90f3-192d-fa0b51f85218@gmail.com \
--to=andrewjmoreton@gmail.com \
--cc=43700@debbugs.gnu.org \
--cc=eliz@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).