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: Mon, 16 Oct 2023 14:29:00 +0300 [thread overview]
Message-ID: <835y36q003.fsf@gnu.org> (raw)
In-Reply-To: <CA+PiuB6i+_cPaYTZS48yuJrjHSp8q+-YggP5x=14WS5+-3W1SA@mail.gmail.com> (message from Erik Overdahl on Sun, 15 Oct 2023 15:03:09 -0500)
> From: Erik Overdahl <erik.overdahl@gmail.com>
> Date: Sun, 15 Oct 2023 15:03:09 -0500
> Cc: 66549@debbugs.gnu.org
>
> I am unable to reproduce this; a manually built shared object still
> crashes for me. I am not sure what steps you took to build the
> grammar.
After cloning the repository, I ran the following commands:
cd src
gcc -O2 -I. -MMD -MF ./parser.d -MP -c -o parser.o parser.c
gcc -O2 -I. -MMD -MF ./scanner.d -MP -c -o scanner.o scanner.c
gcc -shared parser.o scanner.o -ltree-sitter -o libtree-sitter-hcl.dll
(This is on Windows, thus the .dll extension and no -fPIC compiler
switch.) Your link command line, viz.:
cc -fPIC -shared *.o -o libtree-sitter-hcl.so
lacks the -ltree-sitter switch, though, which may or may not be the
problem.
next prev parent reply other threads:[~2023-10-16 11:29 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 [this message]
[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
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=835y36q003.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).