From: Dima Kogan <dima@secretsauce.net>
To: Jeremy Bryant <jb@jeremybryant.net>
Cc: 72165@debbugs.gnu.org
Subject: bug#72165: 31.0.50; Intermittent crashing with recent emacs build
Date: Tue, 23 Jul 2024 14:21:20 -0700 [thread overview]
Message-ID: <87wmlbztwv.fsf@secretsauce.net> (raw)
In-Reply-To: <878qxrbzno.fsf@jeremybryant.net> (Jeremy Bryant's message of "Tue, 23 Jul 2024 21:51:07 +0100")
Jeremy Bryant <jb@jeremybryant.net> writes:
> You mention mu4e twice. Does this happen only with mu4e? mu4e is
> usually distributed separately from Emacs, which version are you
> using?
I don't think mu4e is responsible directly. I ran the april build of
emacs for months with no issues, and only saw the crashes when trying to
debug the *Messages* problem tickled by mu4e. So I doubt somebody else
could readily reproduce the crash. In fact, so far, I haven't been able
to reproduce it either, with the watchpoint enabled. But while debugging
earlier, I saw it crash maybe 4 times within a few hours, so it's
definitely an extant issue.
For the record:
$ dpkg -l mu4e
ii mu4e 1.12.5-1
prev parent reply other threads:[~2024-07-23 21:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 20:56 bug#72165: 31.0.50; Intermittent crashing with recent emacs build Dima Kogan
2024-07-18 1:46 ` bug#72165: More info Dima Kogan
2024-07-18 5:09 ` bug#72165: 31.0.50; Intermittent crashing with recent emacs build Eli Zaretskii
2024-07-18 4:58 ` Eli Zaretskii
2024-07-18 7:25 ` Dima Kogan
2024-07-18 7:38 ` Dima Kogan
2024-07-18 9:07 ` Eli Zaretskii
2024-07-18 9:52 ` Eli Zaretskii
2024-07-19 7:27 ` Dima Kogan
2024-07-29 2:50 ` Dima Kogan
2024-07-29 11:45 ` Eli Zaretskii
2024-07-29 12:49 ` Dima Kogan
2024-07-30 16:21 ` Eli Zaretskii
2024-07-30 20:39 ` Dima Kogan
2024-08-01 11:03 ` Eli Zaretskii
2024-08-01 14:14 ` Dima Kogan
2024-08-05 1:49 ` Dima Kogan
2024-08-05 1:51 ` Dima Kogan
2024-08-05 2:30 ` Eli Zaretskii
2024-07-23 20:51 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-23 21:21 ` Dima Kogan [this message]
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=87wmlbztwv.fsf@secretsauce.net \
--to=dima@secretsauce.net \
--cc=72165@debbugs.gnu.org \
--cc=jb@jeremybryant.net \
/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.