From: Eli Zaretskii <eliz@gnu.org>
To: kirill@korins.ky
Cc: luangruo@yahoo.com, 71712@debbugs.gnu.org, kirill@korins.ky
Subject: bug#71712: 29.3; Crash on OpenBSD
Date: Wed, 26 Jun 2024 16:14:43 +0300 [thread overview]
Message-ID: <86le2r977g.fsf@gnu.org> (raw)
In-Reply-To: <6d1bcb846388ac3d@mx2.catap.net> (message from Kirill A. Korinsky on Wed, 26 Jun 2024 10:11:04 +0100)
> Date: Wed, 26 Jun 2024 10:11:04 +0100
> From: Kirill A. Korinsky <kirill@korins.ky>
> Cc: luangruo@yahoo.com,
> 71712@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...
next prev parent reply other threads:[~2024-06-26 13:14 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-22 0:01 bug#71712: 29.3; Crash on OpenBSD Kirill A. Korinsky
2024-06-22 1:24 ` Stefan Kangas
2024-06-22 7:45 ` Eli Zaretskii
2024-06-22 9:28 ` Kirill A. Korinsky
2024-06-22 10:00 ` Eli Zaretskii
2024-06-22 11:00 ` Kirill A. Korinsky
2024-06-22 12:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-22 14:41 ` Kirill A. Korinsky
2024-06-22 15:55 ` Eli Zaretskii
2024-06-26 9:11 ` Kirill A. Korinsky
2024-06-26 13:14 ` Eli Zaretskii [this message]
2024-06-26 15:58 ` Kirill A. Korinsky
2024-06-26 16:11 ` Eli Zaretskii
2024-06-26 22:00 ` Kirill A. Korinsky
2024-06-27 5:33 ` Eli Zaretskii
2024-06-27 11:44 ` Kirill A. Korinsky
2024-06-27 12:33 ` Eli Zaretskii
2024-06-27 13:36 ` Kirill A. Korinsky
2024-06-27 14:19 ` Gerd Möllmann
2024-06-27 14:43 ` Kirill A. Korinsky
2024-06-27 15:01 ` Gerd Möllmann
2024-06-30 8:52 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-30 16:42 ` Kirill A. Korinsky
2024-06-30 17:40 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-30 22:58 ` Kirill A. Korinsky
2024-07-01 9:10 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-01 11:18 ` Eli Zaretskii
2024-07-01 13:29 ` Kirill A. Korinsky
2024-07-01 13:43 ` Eli Zaretskii
2024-07-01 15:17 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-01 16:04 ` Eli Zaretskii
2024-07-01 16:42 ` Kirill A. Korinsky
2024-07-01 17:36 ` Eli Zaretskii
2024-07-01 18:38 ` Kirill A. Korinsky
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86le2r977g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71712@debbugs.gnu.org \
--cc=kirill@korins.ky \
--cc=luangruo@yahoo.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.