From: Eli Zaretskii <eliz@gnu.org>
To: pavel.buranov@vk.com
Cc: dmitry@gutov.dev, 73648@debbugs.gnu.org
Subject: bug#73648: 29.4; Crash with eglot+gopls and with sly
Date: Sat, 02 Nov 2024 13:43:11 +0200 [thread overview]
Message-ID: <86zfmhyi7k.fsf@gnu.org> (raw)
In-Reply-To: <861q0cmv24.fsf@gnu.org> (message from Eli Zaretskii on Sat, 19 Oct 2024 10:05:39 +0300)
Ping! Ping! Pavel, please respond.
> Cc: dmitry@gutov.dev, 73648@debbugs.gnu.org
> Date: Sat, 19 Oct 2024 10:05:39 +0300
> From: Eli Zaretskii <eliz@gnu.org>
>
> Ping! Pavel, could you please respond, so that we could make progress
> in this issue?
>
> > Cc: 73648@debbugs.gnu.org, pavel.buranov@vk.com
> > Date: Sun, 06 Oct 2024 09:26:42 +0300
> > From: Eli Zaretskii <eliz@gnu.org>
> >
> > > Date: Sun, 6 Oct 2024 04:37:09 +0300
> > > From: Dmitry Gutov <dmitry@gutov.dev>
> > >
> > > On 05/10/2024 22:45, Pavel Buranov via Bug reports for GNU Emacs, the
> > > Swiss army knife of text editors wrote:
> > > > When I normally program in Go with the gopls language server, Emacs
> > > > crashes on autocomplete spots. I can't pin down the precise cases when
> > > > it happens, because it happens spontaneously, but I have learned to type
> > > > very fast in order not to toggle autocompletion. It must be mentioned
> > > > that I use `corfu' with `corfu-auto-delay' set to 0.5 seconds
> > >
> > > Could you try building Emacs from the master branch?
> > >
> > > IIRC at least one crash bug that manifested with Corfu had been fixed in
> > > this release cycle, but it's hard to tell whether that it was the same one.
> >
> > And if the problem persists on master (or if you are unable to build
> > it), please show a backtrace from the crash by running Emacs under
> > GDB, and when it crashes, typing "thread apply all bt" at the GDB
> > prompt.
> >
> > The above assumes that by "crashing" you mean the Emacs process hits a
> > fatal error and is terminated by the OS. If that's not what you mean,
> > then please tell what you mean by "crashes".
> >
> > Thanks.
> >
> >
> >
> >
>
>
>
>
next prev parent reply other threads:[~2024-11-02 11:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-05 19:45 bug#73648: 29.4; Crash with eglot+gopls and with sly Pavel Buranov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-06 1:37 ` Dmitry Gutov
2024-10-06 6:26 ` Eli Zaretskii
2024-10-19 7:05 ` Eli Zaretskii
[not found] ` <1729334534.276949514@f481.i.mail.ru>
2024-10-19 11:00 ` Eli Zaretskii
2024-11-02 11:43 ` Eli Zaretskii [this message]
[not found] ` <1730548307.263868287@f167.i.mail.ru>
2024-11-02 12:12 ` 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=86zfmhyi7k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=73648@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--cc=pavel.buranov@vk.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).