GNU bug report logs - #71712
29.3; Crash on OpenBSD

Previous Next

Full log

Message #35 received at 71712 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: kirill <at> korins.ky
Cc: luangruo <at> yahoo.com, 71712 <at> debbugs.gnu.org, kirill <at> korins.ky
Subject: Re: bug#71712: 29.3; Crash on OpenBSD
Date: Wed, 26 Jun 2024 16:14:43 +0300

> Date: Wed, 26 Jun 2024 10:11:04 +0100
> From: Kirill A. Korinsky <kirill <at> korins.ky>
> Cc: luangruo <at> yahoo.com,
> 	71712 <at> debbugs.gnu.org
> 
> 
> I had upgraded to 29.4, and it had crashed one more time.
> 
> This time the crash had happened when I make a commit into large git
> repository via magit.
> 
> I write commits message in new frame, and after pressing c c to open a frame
> to write commit message, I had switched to another virtual desktop.
> 
> When I've switched back, I hadn't find emacs, but .core was here with the
> same stack trace.
> 
> Inside magit's commit message buffere I use markdown mode.

The way to find the culprit in these cases is to run the recipe with a
watchpoint on the frame cache's 'used' count, and see which code
causes it to be zeroed.  Usually, it is some crazy Lisp run from one
of the hooks which we so graciously offer for grabs.  The tricky part
is to find that code and/or the recipe which could be used to
reproduce the problem at will, which I understand you don't have...

Previous Next

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