unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Erik Overdahl <erik.overdahl@gmail.com>
Cc: 66549@debbugs.gnu.org
Subject: bug#66549: 29.1.50; SIGABRT received parsing file with tree-sitter in PGTK Emacs
Date: Wed, 18 Oct 2023 05:30:07 +0300	[thread overview]
Message-ID: <83edhsoe6o.fsf@gnu.org> (raw)
In-Reply-To: <CA+PiuB7TLsQ1U4fgVW=aJ5kj1bFjYnEvedJgB-K9LmqjgenHnQ@mail.gmail.com> (message from Erik Overdahl on Tue, 17 Oct 2023 16:24:44 -0500)

> From: Erik Overdahl <erik.overdahl@gmail.com>
> Date: Tue, 17 Oct 2023 16:24:44 -0500
> Cc: 66549@debbugs.gnu.org
> 
> I have run the commands (adding -fPIC for linux). I can confirm that using the resulting shared object
> does not crash Emacs. A bit of experimentation reveals that the crash occurs only when the
> grammar is compiled with -O0.

In that case, I think this should be reported to the developers of the
grammar library.  It is not an Emacs problem at all.

> However, despite not crashing, Emacs does not parse the file
> successfully, although I agree this may be a separate issue.

I think this, too, is a problem with the grammar library.





  reply	other threads:[~2023-10-18  2:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-14 20:19 bug#66549: 29.1.50; SIGABRT received parsing file with tree-sitter in PGTK Emacs Erik Overdahl
2023-10-15  5:40 ` Eli Zaretskii
2023-10-15 18:36   ` Erik Overdahl
2023-10-15 19:12     ` Eli Zaretskii
2023-10-15 20:03       ` Erik Overdahl
2023-10-16 11:29         ` Eli Zaretskii
     [not found]           ` <CA+PiuB7EfnM9SG6syhNRGBAMvpr3BH_pgbLtdsU2usVpcvXxyw@mail.gmail.com>
2023-10-17  2:29             ` Eli Zaretskii
2023-10-17 21:24               ` Erik Overdahl
2023-10-18  2:30                 ` Eli Zaretskii [this message]
2023-10-29 11:28                   ` Eli Zaretskii
2023-10-15 19:31     ` Erik Overdahl
2023-10-16 11:22       ` 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=83edhsoe6o.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=66549@debbugs.gnu.org \
    --cc=erik.overdahl@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 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).