all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pip Cet via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: sigve.indregard@pm.me, 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 17:03:37 +0000	[thread overview]
Message-ID: <87sev711ga.fsf@protonmail.com> (raw)
In-Reply-To: <86cymb846o.fsf@gnu.org>

"Eli Zaretskii" <eliz@gnu.org> writes:

>> Cc: 71744@debbugs.gnu.org
>> Date: Wed, 14 Aug 2024 19:03:10 +0300
>> From: Eli Zaretskii <eliz@gnu.org>
>>
>> > 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
>
> Btw, this 0x5555564e3dc0 value is the same as the pointer to old_kbd
> inside read_char:
>
>   #7  read_char (commandflag=0, map=0x0, prev_event=0x0, used_mouse_menu=0x0, end_time=0x7fffffffb5b0) at /usr/src/debug/emacs/emacs-29.4-wayland/src/keyboard.c:3018
> 	  c = <optimized out>
> 	  local_getcjmp = {{__jmpbuf = {93825000405056, -5147324661749537557, 1, 4611686019484352512, 5, 0, -5147324661946669845, -1313834696378178325}, __mask_was_saved = 0, __saved_mask = {__val = {0, 93825010269488, 93825104789632, 140737488335792, 18446744073709550936, 11, 93825104789616, 140737488335856, 140737279378894, 140737488335856, 140737488335920, 0, 140737488335920, 0, 93825010269488, 140737488336000}}}}
> 	  save_jump = {{__jmpbuf = {12048, 140737188459256, 140737488335856, 93825095637120, 16, -7692597586030666240, 48, 1}, __mask_was_saved = 1453957408, __saved_mask = {__val = {140737488335776, 2, 140737488335824, 140737488335760, 140737321006214, 1, 140737321006651, 14319535557742690304, 6, 140737488335696, 140737279373914, 93825000331312, 0, 1, 1, 93823560581122}}}}
> 	  tem = <optimized out>
> 	  save = 0x0
> 	  previous_echo_area_message = 0x0
> 	  also_record = 0x0
> 	  reread = false
> 	  recorded = false
> 	  polling_stopped_here = false
> 	  orig_kboard = 0x5555564e3dc0  <<<<<<<<<<<<<<<<<<<<<<<
>
> So either the value of orig_kboard here is bogus (perhaps due to
> optimizations), or somehow the variable C, which is supposed to hold
> an input event, holds something very different instead, and then it's
> a small surprise that we crash.

I think this looks like a setjmp-related bug. If this sys_setjmp in
read_char:

  specpdl_ref jmpcount = SPECPDL_INDEX ();
  if (sys_setjmp (local_getcjmp))
    {
      /* Handle quits while reading the keyboard.  */

returns true, we goto non_reread, where we test NILP (c). However, 'c'
is not declared volatile, and it might have changed, which would lead to
undefined behavior, including the possibility of holding another value
like orig_kboard.

I'm afraid the only way to know for sure whether there's anything to
that theory is to look at the output of "disass/rs read_char" in gdb,
using the exact same binary that crashed, and check it line by line
(about 3,000 lines here...)

Pip






  parent reply	other threads:[~2024-08-14 17: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
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 [this message]
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=87sev711ga.fsf@protonmail.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=71744@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=pipcet@protonmail.com \
    --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.