From: Eli Zaretskii <eliz@gnu.org>
To: Valtteri Vuorikoski <vuori@notcom.org>
Cc: 40225@debbugs.gnu.org
Subject: bug#40225: 27.0.90; abort with apparent stack explosion in lsp-mode
Date: Tue, 31 Mar 2020 18:53:36 +0300 [thread overview]
Message-ID: <83h7y41pxb.fsf@gnu.org> (raw)
In-Reply-To: <8600e733-d75a-3d8f-897d-2eb3ca6bb59d@notcom.org> (message from Valtteri Vuorikoski on Tue, 31 Mar 2020 16:59:47 +0300)
> Cc: 40225@debbugs.gnu.org
> From: Valtteri Vuorikoski <vuori@notcom.org>
> 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?
next prev parent reply other threads:[~2020-03-31 15:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 14:03 bug#40225: 27.0.90; abort with apparent stack explosion in lsp-mode Valtteri Vuorikoski
2020-03-25 16:20 ` Eli Zaretskii
2020-03-25 16:25 ` Valtteri Vuorikoski
2020-03-25 16:29 ` Eli Zaretskii
2020-03-26 15:42 ` Valtteri Vuorikoski
2020-03-26 18:49 ` Eli Zaretskii
2020-03-31 13:59 ` Valtteri Vuorikoski
2020-03-31 15:53 ` Eli Zaretskii [this message]
2020-03-31 18:39 ` Valtteri Vuorikoski
2020-04-12 10:40 ` Valtteri Vuorikoski
2020-05-15 7:28 ` Valtteri Vuorikoski
2022-02-10 7:21 ` Lars Ingebrigtsen
2022-02-10 9:09 ` Valtteri Vuorikoski
2022-02-10 11:36 ` Lars Ingebrigtsen
2022-02-10 18:50 ` Juri Linkov
2022-02-10 19:49 ` Valtteri Vuorikoski
2022-02-11 8:34 ` Juri Linkov
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=83h7y41pxb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=40225@debbugs.gnu.org \
--cc=vuori@notcom.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).