unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Thu, 26 Mar 2020 20:49:46 +0200	[thread overview]
Message-ID: <835zer9cj9.fsf@gnu.org> (raw)
In-Reply-To: <eace7d79-df57-1352-fc77-9df18d325158@notcom.org> (message from Valtteri Vuorikoski on Thu, 26 Mar 2020 17:42:58 +0200)

> Cc: 40225@debbugs.gnu.org
> From: Valtteri Vuorikoski <vuori@notcom.org>
> Date: Thu, 26 Mar 2020 17:42:58 +0200
> 
> Crash and bt full output from an -O0 -g build, commit 
> e1f0e0892232221e6333b24788b97942c83ec738. Crash occurred after a few 
> hours of Javascript editing in js-mode + tide when switching windows.
> 
> Thread 1 "emacs" received signal SIGSEGV, Segmentation fault.
> 0x0000559b991e133a in pdumper_object_p (obj=<error reading variable: 
> Cannot access memory at address 0x7ffec83b9ff8>) at pdumper.h:145

What do these display?

  (gdb) p/x $sp
  (gdb) p/x &stack_bottom





  reply	other threads:[~2020-03-26 18:49 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 [this message]
2020-03-31 13:59       ` Valtteri Vuorikoski
2020-03-31 15:53         ` Eli Zaretskii
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=835zer9cj9.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).