From: Eli Zaretskii <eliz@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: wkirschbaum@gmail.com, 72863@debbugs.gnu.org, mail@ssbb.me
Subject: bug#72863: 30.0.50; tree-sitter elixir-ts-mode hangs and memory leak on some elixir and heex code
Date: Sun, 08 Sep 2024 10:02:55 +0300 [thread overview]
Message-ID: <86le02wrts.fsf@gnu.org> (raw)
In-Reply-To: <3C53EF6A-EFFA-4648-9741-D7ECAB68F227@gmail.com> (message from Yuan Fu on Sat, 7 Sep 2024 22:57:29 -0700)
> From: Yuan Fu <casouri@gmail.com>
> Date: Sat, 7 Sep 2024 22:57:29 -0700
> Cc: mail@ssbb.me,
> wkirschbaum@gmail.com,
> 72863@debbugs.gnu.org
>
>
>
> > On Sep 7, 2024, at 10:54 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> >
> >> From: Yuan Fu <casouri@gmail.com>
> >> Date: Sat, 7 Sep 2024 22:44:53 -0700
> >> Cc: Wilhelm Kirschbaum <wkirschbaum@gmail.com>,
> >> Eli Zaretskii <eliz@gnu.org>,
> >> 72863@debbugs.gnu.org
> >>
> >> Meanwhile, I want to push the fix for the other bug I discovered to emacs-30. Eli, I wrote a debugging function that prints parser states, naturally this function isn’t called anywhere so there’ll be a compiler warning, what should I do in this case?
> >
> > Why would there be a compiler warning? What kind of warning?
>
> A function-not-used warning. Maybe it’s an lldb thing?
If the function is not static, there should be no such warning.
next prev parent reply other threads:[~2024-09-08 7:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 2:57 bug#72863: 30.0.50; tree-sitter elixir-ts-mode hangs and memory leak on some elixir and heex code mail
2024-08-29 5:09 ` Eli Zaretskii
2024-08-29 6:13 ` Wilhelm Kirschbaum
2024-08-29 6:14 ` Yuan Fu
2024-09-04 6:39 ` Wilhelm Kirschbaum
2024-09-04 7:42 ` mail
2024-09-05 4:32 ` Yuan Fu
2024-09-08 5:44 ` Yuan Fu
2024-09-08 5:54 ` Eli Zaretskii
2024-09-08 5:57 ` Yuan Fu
2024-09-08 7:02 ` Eli Zaretskii [this message]
2024-09-08 7:48 ` Yuan Fu
2024-09-11 3:45 ` Yuan Fu
2024-09-11 19:22 ` mail
2024-09-12 7:47 ` Yuan Fu
2024-09-16 6:58 ` Wilhelm Kirschbaum
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=86le02wrts.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=72863@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=mail@ssbb.me \
--cc=wkirschbaum@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).