GNU bug report logs - #71679
29.3; treesit-node-child function chokes and crashes emacs for nodes with large number of child nodes

Previous Next

Package: emacs;

Reported by: Mauritz Stenek <mstenek <at> disroot.org>

Date: Thu, 20 Jun 2024 15:09:01 UTC

Severity: normal

Found in version 29.3

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Mauritz Stenek <mstenek <at> disroot.org>
Cc: 71679 <at> debbugs.gnu.org
Subject: bug#71679: 29.3; treesit-node-child function chokes and crashes emacs for nodes with large number of child nodes
Date: Thu, 20 Jun 2024 22:43:39 +0300
> From: Mauritz Stenek <mstenek <at> disroot.org>
> Cc: 71679 <at> debbugs.gnu.org
> Date: Thu, 20 Jun 2024 13:31:52 -0600
> 
> On 2024-06-20 at 13:10, Eli Zaretskii <eliz <at> gnu.org> wrote:
> 
> > But your way should also work, if you say "continue" after 
> > attaching
> > GDB.  And don't use -i=mi, since the MI interface is for another
> > program to drive GDB, it is not convenient for humans.
> 
> I couldn't run it your way; running it without the `-i=mi`, this 
> is what I get from gdb:
> 
> ```
> (gdb) continue
> Continuing.
> 
> Thread 1 ".emacs-29.3-rea" received signal SIGSEGV, Segmentation 
> fault.
> 0x0000000000584404 in ?? ()
> (gdb) bt
> #0  0x0000000000584404 in ?? ()
> #1  0x0000000000662d88 in ?? ()
> #2  0x0000000000604b9d in ?? ()
> #3  0x0000000000602b1b in ?? ()
> #4  0x000000000060350d in ?? ()

This means your Emacs is stripped of debug information, so no useful
backtrace is possible.

But never mind: as I wrote earlier, I've reproduced this problem in
the stock Emacs 29.2, and then saw that we already fixed it in the
development sources.




This bug report was last modified 1 year and 28 days ago.

Previous Next


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