From: Eli Zaretskii <eliz@gnu.org>
To: Sigve Indregard <sigve.indregard@pm.me>
Cc: 71744@debbugs.gnu.org
Subject: bug#71744: 29.4; SIGSEGV during completion-at-point in lsp-mode with corfu and cape
Date: Wed, 14 Aug 2024 19:03:10 +0300 [thread overview]
Message-ID: <86ed6r8535.fsf@gnu.org> (raw)
In-Reply-To: <xx7x0Z_rwNEcj4OiuQGtBYWJWr-4-LXoOOJcS5BHeiMe8BKII-ytGa9eADFaWPapHQD9ceac4qC6SCBrXrlZjjYrOyTL5WP5LcCeX9z2Raw=@pm.me> (message from Sigve Indregard on Wed, 14 Aug 2024 15:40:34 +0000)
> Date: Wed, 14 Aug 2024 15:40:34 +0000
> From: Sigve Indregard <sigve.indregard@pm.me>
> Cc: 71744@debbugs.gnu.org
>
> (gdb) frame 3
> #3 parse_modifiers (symbol=XIL(0x5555564e3dc0)) at /usr/src/debug/emacs/emacs-29.4-wayland/src/keyboard.c:6888
> 6888 parse_modifiers (Lisp_Object symbol)
> (gdb) print symbol
> $11 = XIL(0x5555564e3dc0)
> (gdb) xsymbol
> $12 = (struct Lisp_Symbol *) 0xaaaaac1f1640
> Cannot access memory at address 0xaaaaac1f1648
Hmm.. so we need to go up the callstack, but the interesting data
there is all "optimized out". Can you reproduce this in Emacs built
without optimizations (the -O0 switch to the compiler)? If so, please
reproduce the problem and then do:
(gdb) frame 5
(gdb) p idx
(gdb) xtype
If xtype says idx is a cons, try
(gdb) pp idx
to see the event's Lisp representation.
next prev parent reply other threads:[~2024-08-14 16:03 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86ed6r8535.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71744@debbugs.gnu.org \
--cc=sigve.indregard@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.