unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: mstenek@disroot.org
Cc: 71679@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:22:50 +0300	[thread overview]
Message-ID: <86h6dnmnat.fsf@gnu.org> (raw)
In-Reply-To: <86iky3mnvt.fsf@gnu.org> (message from Eli Zaretskii on Thu, 20 Jun 2024 22:10:14 +0300)

> Cc: 71679@debbugs.gnu.org
> Date: Thu, 20 Jun 2024 22:10:14 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> 
> > From: Mauritz Stenek <mstenek@disroot.org>
> > Cc: 71679@debbugs.gnu.org
> > Date: Thu, 20 Jun 2024 13:05:03 -0600
> > 
> > On 2024-06-20 at 12:35, Eli Zaretskii <eliz@gnu.org> wrote:
> > 
> > > Start Emacs from GDB, run your recipe, and when it crashes and 
> > > GDB
> > > kicks in, type
> > >
> > >   (gdb) thread apply all bt
> > >
> > > and post here everything GDB displays as result.
> > 
> > I'm doing this:
> > 
> >     $ gdb -i=mi -p 238975 # the pid of `emacs -q`
> > 
> > but it freezes Emacs and I can't do anything with it.
> 
> You need to say "continue" to let Emacs continue running after you
> attach the debugger.
> 
> > Is this how you "Start Emacs from GDB"?
> 
> No, I usually start GDB first:
> 
>   $ gdb ./emacs
>   ...
>   (gdb) run -Q
> 
> 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.

Actually, forget it.  I've succeeded in reproducing this here, and I
see that this problem was already fixed in the development sources.
The next Emacs release will have the bug fixed.

So I think we can close this bug.





  reply	other threads:[~2024-06-20 19:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20 15:08 bug#71679: 29.3; treesit-node-child function chokes and crashes emacs for nodes with large number of child nodes Mauritz Stenek via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-20 16:02 ` Eli Zaretskii
     [not found]   ` <877cejmv0m.fsf@disroot.org>
2024-06-20 16:50     ` Eli Zaretskii
2024-06-20 17:07       ` Mauritz Stenek via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-20 18:06         ` Eli Zaretskii
2024-06-20 18:24           ` Mauritz Stenek via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-20 18:35             ` Eli Zaretskii
2024-06-20 19:05               ` Mauritz Stenek via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-20 19:10                 ` Eli Zaretskii
2024-06-20 19:22                   ` Eli Zaretskii [this message]
2024-06-20 19:46                     ` Mauritz Stenek via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-21  5:55                       ` Eli Zaretskii
2024-06-20 20:23                     ` Mauritz Stenek via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-21  6:04                       ` Eli Zaretskii
2024-06-20 19:31                   ` Mauritz Stenek via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-20 19:43                     ` 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=86h6dnmnat.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=71679@debbugs.gnu.org \
    --cc=mstenek@disroot.org \
    /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).