From: Eli Zaretskii <eliz@gnu.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: eggert@cs.ucla.edu, monnier@iro.umontreal.ca, 57699@debbugs.gnu.org
Subject: bug#57699: Assertion failure "lib_child_handler != dummy_handler"
Date: Sun, 11 Sep 2022 14:47:34 +0300 [thread overview]
Message-ID: <834jxe9lpl.fsf@gnu.org> (raw)
In-Reply-To: <87pmg22lai.fsf@tcd.ie> (bug-gnu-emacs@gnu.org)
> Cc: eggert@cs.ucla.edu, monnier@iro.umontreal.ca
> Date: Sun, 11 Sep 2022 14:38:29 +0300
> From: "Basil L. Contovounesios" via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> > Stefan's patch looks good so I installed it (with my comments :-).
>
> Thanks.
>
> Building emacs-28 on Debian fails with the same fatal error:
>
Then use the same patch.
> Can the fix be backported?
It's too late for Emacs 28.2, I think, but we can look into
backporting it afterwards. (I'm not very worried about 28.2, since
I'm sure the distros will pick up the change regardless.)
next prev parent reply other threads:[~2022-09-11 11:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 14:40 bug#57699: Assertion failure "lib_child_handler != dummy_handler" Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-09 14:59 ` Robert Pluim
2022-09-09 15:27 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-09 17:13 ` Lars Ingebrigtsen
2022-09-09 21:27 ` Paul Eggert via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-11 11:38 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-11 11:47 ` Eli Zaretskii [this message]
2022-09-11 13:54 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-11 14:51 ` Paul Eggert 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=834jxe9lpl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=57699@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=eggert@cs.ucla.edu \
--cc=monnier@iro.umontreal.ca \
/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.