unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Sat, 03 Oct 2020 17:02:47 +0300	[thread overview]
Message-ID: <83mu13flvc.fsf@gnu.org> (raw)
In-Reply-To: <9902f5c5-ca88-4e70-a436-f8f471f723f7@gmail.com> (message from Andy Moreton on Sat, 3 Oct 2020 14:40:47 +0100)

> Cc: 43700@debbugs.gnu.org
> From: Andy Moreton <andrewjmoreton@gmail.com>
> Date: Sat, 3 Oct 2020 14:40:47 +0100
> 
> No - watchpoints seem to be completely broken in this build of gdb: 
> hardware watchpoints don't work, and if software watchpoints work then I 
> do not have the patience to wait for hours for them to fire.

Strange.  I see no reports of this problem on the Internet.  What
version of GDB is that?  Maybe try to downgrade to a previous one?

> > Another possibility is that the face cache gets reset not for the new
> > frame being created, but for the other frame.  You can tell by
> > comparing the value of 'f' at the point where init_frame_faces is
> > called and at the segfault point.  If this is what happens, then we
> > will need a slightly more sophisticated method of setting the
> > watchpoint.
> 
> True, but not much use without working watchpoints.

Does it help to set a breakpoint in free_realized_faces instead?  Also
in uncache_face, here:

  if (face->id == c->used)
    --c->used;

The last one could be conditioned on c->used == 1 (before the
decrement).





  reply	other threads:[~2020-10-03 14:02 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
2020-10-03 12:45                   ` Eli Zaretskii
2020-10-03 13:40                     ` Andy Moreton
2020-10-03 14:02                       ` Eli Zaretskii [this message]
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=83mu13flvc.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).