From: Joost Kremers <joostkremers@fastmail.fm>
To: emacs-devel@gnu.org
Subject: tree-sitter crashes Emacs
Date: Thu, 25 Apr 2024 08:58:45 +0200 [thread overview]
Message-ID: <86wmokcp3c.fsf@p200300d6272f170fb9ce529a1eae86f3.dip0.t-ipconnect.de> (raw)
Hi list,
A week ago or so, I opened a Python file in Emacs and saw Emacs crash hard.
Bisecting my init file, I found that the culprit was tree-sitter. As it turns
out, some change was made in tree-sitter that caused the ABI to change, and when
I upgraded my distro's tree-sitter package, the new ABI caused Emacs to crash.
There is a thread about this issue on the tree-sitter GitHub page:
https://github.com/tree-sitter/tree-sitter/issues/3296
The consensus there seems to be, however, that the current problem should not be
solved by the tree-sitter project, but rather by the relevant Linux
distributions and/or by Emacs itself.
A bug has been opened for Arch Linux (the distro I'm using):
https://gitlab.archlinux.org/archlinux/packaging/packages/emacs/-/issues/2
That issue, however, is labelled with "status:waiting-upstream", which suggests
that nothing's going to happen until the tree-sitter project does something.
Which is not going to happen, I fear, because the tree-sitter issue has been
closed.
Since I haven't seen the issue mentioned here and given that it was suggested it
might be an Emacs issue, I wanted to ask the opinion of the maintainers: can
this be considered an Emacs bug, or is it really something that should be solved
upstream?
TIA
--
Joost Kremers
Life has its moments
next reply other threads:[~2024-04-25 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 6:58 Joost Kremers [this message]
2024-04-26 14:53 ` tree-sitter crashes Emacs Eli Zaretskii
2024-04-28 12:48 ` Joost Kremers
2024-04-28 13:50 ` Eli Zaretskii
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=86wmokcp3c.fsf@p200300d6272f170fb9ce529a1eae86f3.dip0.t-ipconnect.de \
--to=joostkremers@fastmail.fm \
--cc=emacs-devel@gnu.org \
/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).