From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Gregor Zattler <telegraph@gmx.net>,
Stefan Monnier <monnier@iro.umontreal.ca>,
59183@debbugs.gnu.org
Subject: bug#59183: 29.0.50; emacs_abort () at sysdep.c:2313
Date: Sat, 12 Nov 2022 21:26:14 +0800 [thread overview]
Message-ID: <87bkpcmhhl.fsf@yahoo.com> (raw)
In-Reply-To: <834jv6r42m.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 10 Nov 2022 21:40:17 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> #0 terminate_due_to_signal (sig=6, backtrace_limit=40) at emacs.c:421
>> #1 0x000055555579def5 in emacs_abort () at sysdep.c:2313
>> #2 0x00005555559324d6 in itree_iterator_start (tree=0x555556e65850, begin=359683, end=592913, order=ITREE_ASCENDING, file=0x5555559eca4f "buffer.c", line=2982) at itree.c:1161
>> #3 0x00005555557ae9ef in overlays_in (beg=359683, end=359684, extend=false, vec_ptr=0x7fffffff18c0, len_ptr=0x7fffffff1910, empty=false, trailing=true, next_ptr=0x0) at buffer.c:2982
>> #4 0x00005555557aebed in overlays_at (pos=359683, extend=false, vec_ptr=0x7fffffff18c0, len_ptr=0x7fffffff1910, next_ptr=0x0) at buffer.c:3035
>> #5 0x0000555555646226 in note_mouse_highlight (f=0x5555590388f0, x=181, y=321) at xdisp.c:35144
>> #6 0x000055555570b846 in x_note_mouse_movement (frame=0x5555590388f0, event=0x7fffffff1f20, device=XIL(0x5555563b5cd4)) at xterm.c:14137
>> #7 0x000055555571ab35 in handle_one_xevent (dpyinfo=0x55555a326240, event=0x7fffffff2380, finish=0x7fffffff2370, hold_quit=0x7fffffff24a0) at xterm.c:22381
>> #8 0x000055555571f577 in XTread_socket (terminal=0x5555572511a0, hold_quit=0x7fffffff24a0) at xterm.c:24551
>> #9 0x000055555577d39a in gobble_input () at keyboard.c:7368
>> #10 0x000055555577d997 in handle_async_input () at keyboard.c:7599
>> #11 0x000055555577d9b6 in process_pending_signals () at keyboard.c:7613
>> #12 0x00005555558580cb in probably_quit () at eval.c:1661
>> #13 0x000055555586383d in maybe_quit () at lisp.h:3684
>> #14 0x000055555586ac7c in Fassq (key=XIL(0x5d00), alist=XIL(0x5555594ef1f3)) at fns.c:1931
>> #15 0x000055555590c41d in lookup_char_property (plist=XIL(0x555560375da3), prop=XIL(0x5d00), textprop=false) at intervals.c:1735
>> #16 0x00005555557b1dc8 in Foverlay_get (overlay=XIL(0x555560371dcd), prop=XIL(0x5d00)) at buffer.c:3934
>> #17 0x0000555555911dc1 in get_char_property_and_overlay (position=make_fixnum(359631), prop=XIL(0x5d00), object=XIL(0x55555e02d465), overlay=0x7fffffff2768) at textprop.c:649
>
> Stefan, I think we must lift the restriction of "only one itree
> iteration at a time", otherwise we will keep bumping into situations
> like this one. It isn't hard to imagine other cases where some code
> wants to look up overlays while some of the callers is in the middle
> of something similar; handling the mouse-highlight is just one such
> example. We never had restrictions in Emacs on simultaneous multiple
> read-only access to overlays, and it makes no sense to introduce such
> restrictions now.
>
> This has to be fixed before Emacs 29.
+1. I just hit this bug as well.
Would someone please sum up why itree iteration is not reentrant right
now?
TIA.
next prev parent reply other threads:[~2022-11-12 13:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 18:55 bug#59183: 29.0.50; emacs_abort () at sysdep.c:2313 Gregor Zattler
2022-11-10 19:40 ` Eli Zaretskii
2022-11-12 13:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-11-12 18:24 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-17 23:54 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] <87357z6fqc.fsf@devnulllabs.io>
[not found] ` <jwv5ycvg087.fsf-monnier+emacs@gnu.org>
2023-01-25 17:17 ` Kenny Ballou
2023-01-25 20:58 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-30 18:03 ` Kenny Ballou
2023-01-30 19:15 ` Stefan Monnier 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bkpcmhhl.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=59183@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=monnier@iro.umontreal.ca \
--cc=telegraph@gmx.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.