Subject: Re: bug#40225: 27.0.90; abort with apparent stack explosion in lsp-mode

From: Eli Zaretskii <[email-masked]>
Date: Tue, 31 Mar 2020 18:53:36 +0300

> Cc: [email-masked]
> From: Valtteri Vuorikoski <[email-masked]>
> Date: Tue, 31 Mar 2020 16:59:47 +0300
> 
> Thread 1 "emacs" received signal SIGSEGV, Segmentation fault.
> 0x00005568e2e5dc1b in mark_object (arg=<error reading variable: Cannot 
> access memory at address 0x7ffde9c2fff8>) at alloc.c:6386
> 6386    {
> (gdb) p/x $sp
> $1 = 0x7ffde9c2fff0
> (gdb) p/x &stack_bottom
> No symbol "stack_bottom" in current context.

What about this one:

  (gdb) p &(current_thread->stack_bottom)

> (gdb) bt full 3
> #0  0x00005568e2e5dc1b in mark_object (arg=Python Exception <class 
> 'gdb.MemoryError'> Cannot access memory at address 0x7ffde9c2fff8:
> #1  0x00005568e2e5df9c in mark_object (arg=0x5568e6c1f003) at alloc.c:6629
>          ptr = 0x5568e6c1f000
>          obj = 0x5568e6c1f043
>          po = 0x5568e6c1f000
>          cdr_count = 0

This does look like stack overflow.  Can you enlarge the stack size of
your Emacs and see if that helps?