unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: alexis purslane <alexispurslane@pm.me>
Cc: 71073@debbugs.gnu.org
Subject: bug#71073: Emacs segfaults if corfu is asked to autocomplete something while the LSP server providing completions is still starting/indexing
Date: Mon, 20 May 2024 14:02:12 +0300	[thread overview]
Message-ID: <86ttisagqz.fsf@gnu.org> (raw)
In-Reply-To: <Eyqu8A_qFB4NFIgmwO0ISo99LfmbfzT4hz4DgxgMVzHd9C4rgJJfnSHTLNW0SmoAhGymWilJkvd6aQviA5rbONSgRra92_hVjQO2eZfNcpM=@pm.me> (bug-gnu-emacs@gnu.org)

> Date: Sun, 19 May 2024 19:58:23 +0000
> From:  alexis purslane via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> If corfu is prompted to start autocompletion (by typing the first 3
> letters of a word in my case) while an eglot LSP server is still
> starting up, but after eglot has connected to that server, you get a
> segmentation fault.
> 
> ## Steps to reproduce
> 
> 1. Open a file with a mode associated with it that has a language server
> 2. {M-x eglot}
> 3. Before the server has finished indexing and can provide completions,
>    but after it has connected, prompt corfu to do an autocompletion
> 4. Enjoy your segfault salad
> 
> ## Debug information
> 
> Here's the backtrace from the core dump:

Thanks, but this backtrace is less useful than it could be.  If you
can run Emacs from GDB, please do that, and when it segfaults and GDB
shows its prompt, type

  (gdb) thread apply all bt

and post here everything GDB produces as result.





  reply	other threads:[~2024-05-20 11:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-19 19:58 bug#71073: Emacs segfaults if corfu is asked to autocomplete something while the LSP server providing completions is still starting/indexing alexis purslane via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-20 11:02 ` Eli Zaretskii [this message]
     [not found]   ` <R1HuOgwSHJv2VUkxKdJA3LS2xZ7FEx4a27F4R4JexO5HGWWVgufaEgOXfhGgZmc12YJ6LSueosCSPJhCUGQgLaIGUasgZSJyzm3tvV56sko=@pm.me>
2024-05-21 18:21     ` Eli Zaretskii
     [not found]       ` <jqvaDt-RQv2Jvca3QEodr0RZhLmXYQk4MySVNDiuYZrBt0P9UdlU7X1XniiPztKUIzb2kFzSXD8rHGRhuHTMZ7t6MWOVXHHbd6Hd7Iw8cDc=@pm.me>
2024-05-21 18:47         ` Eli Zaretskii
2024-05-21 18:54           ` alexis purslane via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-22 11:01             ` Eli Zaretskii
2024-05-22 11:03               ` alexis purslane via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-22 11:36           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-25  9:08             ` Eli Zaretskii
2024-05-25 23:57               ` alexis purslane via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-26  8:56                 ` Stefan Kangas

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=86ttisagqz.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=71073@debbugs.gnu.org \
    --cc=alexispurslane@pm.me \
    /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).