all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier 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>, 59183@debbugs.gnu.org
Subject: bug#59183: 29.0.50; emacs_abort () at sysdep.c:2313
Date: Thu, 17 Nov 2022 18:54:46 -0500	[thread overview]
Message-ID: <jwvbkp5p27o.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <834jv6r42m.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 10 Nov 2022 21:40:17 +0200")

> 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.

I just pushed to `master` a new code for ITREE_FOREACH which
is reentrant.  It should fix those problems, and hopefully won't
introduce new ones.

Please confirm,


        Stefan






  parent reply	other threads:[~2022-11-17 23:54 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
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 [this message]
     [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=jwvbkp5p27o.fsf-monnier+emacs@gnu.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=59183@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --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.