GNU bug report logs - #60237
30.0.50; tree sitter core dumps when I edebug view a node

Previous Next

Package: emacs;

Reported by: Mickey Petersen <mickey <at> masteringemacs.org>

Date: Wed, 21 Dec 2022 12:30:02 UTC

Severity: normal

Found in version 30.0.50

Done: Stefan Monnier <monnier <at> iro.umontreal.ca>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Yuan Fu <casouri <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Mickey Petersen <mickey <at> masteringemacs.org>, 60237 <at> debbugs.gnu.org
Subject: bug#60237: 30.0.50; tree sitter core dumps when I edebug view a  node
Date: Sat, 24 Dec 2022 01:20:19 -0800
Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Mickey Petersen <mickey <at> masteringemacs.org>
>> Date: Wed, 21 Dec 2022 12:24:34 +0000
>
> Yuan, can you look into this?  The crash is in tree-sitter, so maybe
> it isn't our bug, but I'd like to be sure.  And even if it is a
> tree-sitter bug, maybe we can work around it to prevent Emacs from
> crashing?

Absolutely.

>> Happens in emacs -Q (after loading some simple elisp code that uses treesit.el) and consistently and repeatedly.
>> 
>> 
>> Here's the elisp. When I edebug it I can step and view all the
>> variables and expressions I like. The `combobulate-' functions are
>> widely used in the library and pose no issues anywhere else and do
>> nothing more than fetch nodes via tree sitter. It is only this bit of
>> code that blows up, and then only when invoked inside a python
>> string.

It would be nice if you can make a reproduce recipe. Judging from the
backtrace, you can probably trigger it by printing the node with print
or princ.  And does it trigger on all python strings? Or some specific
string in some specific python source?

Yuan




This bug report was last modified 2 years and 107 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.