all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 58296@debbugs.gnu.org
Subject: bug#58296: 29.0.50; "menu.c:120: Emacs fatal error: assertion failed: !menu_items_inuse" on macOS 10.13.6
Date: Wed, 05 Oct 2022 08:46:15 +0300	[thread overview]
Message-ID: <83v8oyu8k8.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmm4XEDT49-2QGKEqX4HpntrWXbvGf8=MmPe=zw3Pg3tGg@mail.gmail.com> (message from Stefan Kangas on Wed, 5 Oct 2022 00:11:25 +0200)

> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Wed, 5 Oct 2022 00:11:25 +0200
> 
> Run "emacs -Q", type "M-x ns-print-buffer" to print, press either
> "Yes" or "No" (or type ESC).
> 
> Emacs crashes with this printed on terminal:
> 
>     menu.c:120: Emacs fatal error: assertion failed: !menu_items_inuse
>     Fatal error 6: Aborted
>     Abort trap: 6
> 
> gdb backtrace:
> 
> Thread 3 hit Breakpoint 1, terminate_due_to_signal (sig=6,
> backtrace_limit=2147483647) at emacs.c:421
> 421      signal (sig, SIG_DFL);
> (gdb) bt
> #0  terminate_due_to_signal (sig=6, backtrace_limit=2147483647) at emacs.c:421
> #1  0x00000001002b73ce in die (msg=0x10052cd9e "!menu_items_inuse",
> file=0x10052cdb0 "menu.c", line=120) at alloc.c:7672
> #2  0x00000001000ebbe2 in discard_menu_items () at menu.c:120
> #3  0x00000001004cc2c4 in pop_down_menu (arg=0x1035e5170) at nsmenu.m:1554

Isn't this due to the same reason as bug#58288?  The NS build tries to
use a popup menu that no code has set up correctly, or whose data was
deleted/GCed.





  reply	other threads:[~2022-10-05  5:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04 22:11 bug#58296: 29.0.50; "menu.c:120: Emacs fatal error: assertion failed: !menu_items_inuse" on macOS 10.13.6 Stefan Kangas
2022-10-05  5:46 ` Eli Zaretskii [this message]
2022-10-06  2:54 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-06  8:39   ` Robert Pluim
2022-10-06  9:31   ` Stefan Kangas

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=83v8oyu8k8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=58296@debbugs.gnu.org \
    --cc=stefankangas@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 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.