From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 58288@debbugs.gnu.org, larsi@gnus.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 16:47:39 +0300 [thread overview]
Message-ID: <83mtabvgxw.fsf@gnu.org> (raw)
In-Reply-To: <87zgeb91ac.fsf@gmail.com> (message from Robert Pluim on Tue, 04 Oct 2022 15:16:43 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: Lars Ingebrigtsen <larsi@gnus.org>, 58288@debbugs.gnu.org,
> ajd2195@columbia.edu
> Date: Tue, 04 Oct 2022 15:16:43 +0200
>
> >>>>> On Tue, 04 Oct 2022 15:32:00 +0300, Eli Zaretskii <eliz@gnu.org> said:
>
> >> 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.
>
> Eli> If you or someone else could show a meaningful backtrace, maybe the
> Eli> reason will become evident.
>
> (this is not current master. I doubt that changes things, but I can
> recompile if needed)
>
> Process 48138 stopped
> * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x3)
> frame #0: 0x00000001000743b0 emacs`find_and_return_menu_selection [inlined] AREF(array=<unavailable>, idx=0) at lisp.h:1941:10 [opt]
> 1938 AREF (Lisp_Object array, ptrdiff_t idx)
> 1939 {
> 1940 eassert (0 <= idx && idx < gc_asize (array));
> -> 1941 return XVECTOR (array)->contents[idx];
> 1942 }
> 1943
> 1944 INLINE Lisp_Object *
> Target 0: (emacs) stopped.
> warning: emacs was compiled with optimization - stepping may behave oddly; variables may not be available.
> (lldb) bt
> * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x3)
> * frame #0: 0x00000001000743b0 emacs`find_and_return_menu_selection [inlined] AREF(array=<unavailable>, idx=0) at lisp.h:1941:10 [opt]
> frame #1: 0x00000001000743b0 emacs`find_and_return_menu_selection(f=0x00000001040cde30, keymaps=false, client_data=0x0000000103071c80) at menu.c:988:17 [opt]
> frame #2: 0x0000000100249fce emacs`-[EmacsMenu runMenuAt:forFrame:keymaps:](self=0x000060000175d840, _cmd=<unavailable>, p=(x = 86, y = 464), f=0x00000001040cde30, keymaps=false) at nsmenu.m:767:9 [opt]
This is in NS-specific code for popup menus. Sounds like no one is
setting up the menu_items array in that case?
next prev parent reply other threads:[~2022-10-04 13:47 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
2022-10-04 13:16 ` Robert Pluim
2022-10-04 13:47 ` Eli Zaretskii [this message]
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=83mtabvgxw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58288@debbugs.gnu.org \
--cc=ajd2195@columbia.edu \
--cc=larsi@gnus.org \
--cc=rpluim@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).