From: Andrea Corallo <acorallo@gnu.org>
To: Anton Frolov <frolov.mr@gmail.com>
Cc: 72599@debbugs.gnu.org
Subject: bug#72599: 29.4; Emacs crushes with segfault
Date: Tue, 13 Aug 2024 04:31:52 -0400 [thread overview]
Message-ID: <yp1h6boj01z.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <c9de3b69-1b74-4272-8e4f-bf9bff56d572@gmail.com> (Anton Frolov's message of "Mon, 12 Aug 2024 21:40:58 +0300")
Hi Anton,
how did you reached the situation of the crash? Can you provide a
reproducer for it [1]?
Do you still see this on emacs-30? I believe there will be no more
releases based on 29.
Thanks
Andrea
[1] <https://www.gnu.org/software/emacs/manual/html_node/emacs/Checklist.html#Checklist>
next prev parent reply other threads:[~2024-08-13 8:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 18:40 bug#72599: 29.4; Emacs crushes with segfault Anton Frolov
2024-08-13 8:31 ` Andrea Corallo [this message]
2024-08-13 12:17 ` Eli Zaretskii
2024-08-13 17:14 ` Anton Frolov
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=yp1h6boj01z.fsf@fencepost.gnu.org \
--to=acorallo@gnu.org \
--cc=72599@debbugs.gnu.org \
--cc=frolov.mr@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).