GNU bug report logs - #43700
28.0.50; Crash creating a second frame

Previous Next

Package: emacs;

Reported by: Andy Moreton <andrewjmoreton <at> gmail.com>

Date: Tue, 29 Sep 2020 10:48:01 UTC

Severity: normal

Found in version 28.0.50

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andy Moreton <andrewjmoreton <at> gmail.com>
Cc: 43700 <at> debbugs.gnu.org
Subject: bug#43700: 28.0.50; Crash creating a second frame
Date: Sat, 03 Oct 2020 15:45:55 +0300
> Cc: 43700 <at> debbugs.gnu.org
> From: Andy Moreton <andrewjmoreton <at> gmail.com>
> Date: Sat, 3 Oct 2020 13:26:09 +0100
> 
> >    (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 :-(

Does the watchpoint fire if you remove the condition?  IOW, do this:

    (gdb) watch -l f->face_cache->used

If this works, then you should see also the events where faces are
added, which will show the 'used' count go up.

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.

Thanks.




This bug report was last modified 4 years and 282 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.