From: Ravi D'Elia <ravijdelia@gmail.com>
To: 72025@debbugs.gnu.org
Subject: bug#72025: SEGFAULT when using corfu and lsp-mode with clangd
Date: Wed, 10 Jul 2024 20:18:56 -0400 [thread overview]
Message-ID: <ceu6mjxvkywrze4gyxzp36yfemvejt5wcf6rv5e2sggcvy4pq2@imfshloddfti> (raw)
In-Reply-To: <mc6mc7js7n3tfiarnsfdk4ylctg6fp3dsfgqcghifyc3ggkgtk@6tnbdedlcfsx>
On 24/07/10 11:27AM, Ravi D'Elia wrote:
>Sorry about the backtrace, I did indeed use gdb but didn't have
>the debugging symbols to make it useful. My distro (arch) does
>ship a stripped binary with a separate debug package but I'm having
>difficulties due to (I think) some packaging mishap on my end. While
>I take that up on my distro's forum, I'm going to try and build with
>debugging info. I'll send in the backtrace when one of these bears
>fruit. Didn't expect to have my computer on me, otherwise I would have
>figured this out first.
Well after a day of trying I have found a very robust solution to the
problem- include debug symbols in any way whatsoever. I have failed to
replicate with an emacs binary built with any combination of flags and
settings. I have failed to replicate with what should be an exact rebuild
of Arch's package. The only way I get the error is by reinstalling from
repos. So I'm calling it, I'll just use the working build for now. Since
that build has debug symbols it will be easy to get some useful data if
the problem strikes again, but for now there isn't much to do. Thanks
for the help, sorry I couldn't do more.
next prev parent reply other threads:[~2024-07-11 0:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 23:20 bug#72025: SEGFAULT when using corfu and lsp-mode with clangd Ravi D'Elia
2024-07-10 8:06 ` Andrea Corallo
2024-07-10 11:57 ` Eli Zaretskii
2024-07-10 14:07 ` Andrea Corallo
2024-07-10 14:37 ` Eli Zaretskii
2024-07-10 15:27 ` Ravi D'Elia
2024-07-11 0:18 ` Ravi D'Elia [this message]
2024-07-11 4:55 ` 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=ceu6mjxvkywrze4gyxzp36yfemvejt5wcf6rv5e2sggcvy4pq2@imfshloddfti \
--to=ravijdelia@gmail.com \
--cc=72025@debbugs.gnu.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).