unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Matthew Rothlisberger <mattjrothlis@gmail.com>
Cc: 71744@debbugs.gnu.org
Subject: bug#71744: 29.4; SIGSEGV during completion-at-point in lsp-mode with corfu and cape
Date: Thu, 27 Jun 2024 13:05:19 +0300	[thread overview]
Message-ID: <867cea66qo.fsf@gnu.org> (raw)
In-Reply-To: <CAG3xYBB1dn5E+S0NkdEAUza_EuBwkWkO8ERik9Os+JcDqcsEdQ@mail.gmail.com> (message from Matthew Rothlisberger on Wed, 26 Jun 2024 19:27:00 -0400)

> From: Matthew Rothlisberger <mattjrothlis@gmail.com>
> Date: Wed, 26 Jun 2024 19:27:00 -0400
> Cc: 71744@debbugs.gnu.org
> 
> Thanks for your reply.
> 
> > On Mon, Jun 24, 2024 at 08:28  Eli Zaretskii <eliz@gnu.org> wrote:
> > Thanks, but we need a full GDB backtrace in order to investigate this, since your use case involves a lot of
> moving parts that are not part of Emacs.
> 
> Here's GDB output after triggering the crash:
> 
> Thread 1 "emacs" received signal SIGSEGV, Segmentation fault.
> Fget (symbol=XIL(0x555555f430d0), propname=XIL(0x6a20))
>     at /usr/src/debug/emacs/emacs-29.4/src/lisp.h:1152
> 1152  return p;
> (gdb) bt full
> #0  Fget (symbol=XIL(0x555555f430d0), propname=XIL(0x6a20)) at
> /usr/src/debug/emacs/emacs-29.4/src/lisp.h:1152
>         propval = <optimized out>
>         propval = <optimized out>
> #1  Fget (symbol=XIL(0x555555f430d0), propname=XIL(0x6a20)) at
> /usr/src/debug/emacs/emacs-29.4/src/fns.c:2516
>         propval = <optimized out>
> #2  0x0000555555727621 in parse_modifiers (symbol=XIL(0x555555f430d0)) at
> /usr/src/debug/emacs/emacs-29.4/src/keyboard.c:6897
>         elements = <optimized out>
>         elements = <optimized out>
>         end = <optimized out>
>         modifiers = <optimized out>
>         unmodified = <optimized out>
>         mask = <optimized out>
> #3  parse_modifiers (symbol=XIL(0x555555f430d0)) at
> /usr/src/debug/emacs/emacs-29.4/src/keyboard.c:6888
>         elements = <optimized out>
>         end = <optimized out>
>         modifiers = <optimized out>
>         unmodified = <optimized out>
>         mask = <optimized out>
> #4  0x00005555557377b8 in reorder_modifiers (symbol=<optimized out>) at
> /usr/src/debug/emacs/emacs-29.4/src/keyboard.c:7028
>         parsed = <optimized out>
>         parsed = <optimized out>

Thanks.  I don't see any obvious reasons for the crash, sorry, not
with so many variables "optimized out".  I do notice that your build
was done with many non-default compilation and link switches, so maybe
one of them causes this in some way.

Perhaps try reproducing this in an unoptimized build, maybe this will
give us more information regarding where and why this happens.

You mentioned earlier this doesn't happen in Emacs 31, does it mean
the master branch of the Emacs Git repository doesn't have this
problem?  How about the emacs-30 release branch (which will become
Emacs 30.1)?





  reply	other threads:[~2024-06-27 10:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-23 21:16 bug#71744: 29.4; SIGSEGV during completion-at-point in lsp-mode with corfu and cape Matthew Rothlisberger
2024-06-24 12:28 ` Eli Zaretskii
2024-06-26 23:27   ` Matthew Rothlisberger
2024-06-27 10:05     ` Eli Zaretskii [this message]
2024-08-14 13:22 ` Sigve Indregard via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-14 13:57   ` Eli Zaretskii
2024-08-14 15:40     ` Sigve Indregard via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-14 16:03       ` Eli Zaretskii
2024-08-14 16:22         ` Eli Zaretskii
2024-08-14 16:37           ` Sigve Indregard via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-14 17:03           ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-15  9:07           ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-16 15:08             ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-17  4:37               ` Paul Eggert
2024-08-17  6:14                 ` Eli Zaretskii
2024-08-17 18:23                   ` Paul Eggert
2024-08-17  7:46                 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-17 18:27                   ` Paul Eggert

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=867cea66qo.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=71744@debbugs.gnu.org \
    --cc=mattjrothlis@gmail.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).