From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 58288@debbugs.gnu.org, ajd2195@columbia.edu
Subject: bug#58288: 29.0.50; (flyspell-correct-word-before-point) followed by <down> crashes emacs
Date: Tue, 04 Oct 2022 15:32:00 +0300 [thread overview]
Message-ID: <83tu4jvkfz.fsf@gnu.org> (raw)
In-Reply-To: <877d1f3kgj.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue, 04 Oct 2022 13:19:08 +0200)
> Cc: 58288@debbugs.gnu.org
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Tue, 04 Oct 2022 13:19:08 +0200
>
> Andrew John De Angelis <ajd2195@columbia.edu> writes:
>
> > - emacs -Q
> > - Eval: (turn-on-flyspell)
>
> Or `M-x flyspell-mode'.
>
> > - write a word that's not present in the dictionary
> > (I wrote "incorrectlll")
> > - place cursor at word
> > - M-x flyspell-correct-word-before-point
> > - press down arrow (<down>) to navigate to the 'Save word' option
> > - emacs crashes
> > (in the terminal, this is the message:
> > Fatal error 11: Segmentation fault
> > zsh: abort emacs -Q
>
> I can reproduce this crash on Macos (but not on Ubuntu) with the current
> "master".
>
> However, I'm not well versed in debugging stuff like this on Macos, so
> if somebody else could have a look, that'd be great.
If you or someone else could show a meaningful backtrace, maybe the
reason will become evident.
next prev parent reply other threads:[~2022-10-04 12:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 21:20 bug#58288: 29.0.50; (flyspell-correct-word-before-point) followed by <down> crashes emacs Andrew John De Angelis
2022-10-04 11:19 ` Lars Ingebrigtsen
2022-10-04 12:32 ` Eli Zaretskii [this message]
2022-10-04 13:16 ` Robert Pluim
2022-10-04 13:47 ` Eli Zaretskii
2022-10-04 15:14 ` Robert Pluim
2022-10-04 16:30 ` Eli Zaretskii
2022-10-05 10:01 ` Robert Pluim
2022-10-05 10:06 ` Eli Zaretskii
2022-10-05 10:29 ` Robert Pluim
2022-10-05 10:46 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-05 13:53 ` Robert Pluim
2022-10-06 2:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83tu4jvkfz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58288@debbugs.gnu.org \
--cc=ajd2195@columbia.edu \
--cc=larsi@gnus.org \
/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).