unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dennis Mayr <dennis.mayr.c@gmail.com>
Cc: 33257@debbugs.gnu.org
Subject: bug#33257: 26.1; Emacs 26.1 crashes with SEGFAULT under markdown-mode while opening large file
Date: Sun, 04 Nov 2018 20:35:30 +0200	[thread overview]
Message-ID: <835zxceln1.fsf@gnu.org> (raw)
In-Reply-To: <CANpx60wsXi_TX66vT6eZFNTmXSWn_7xG0EaH70qTkQLXrQL7rw@mail.gmail.com> (message from Dennis Mayr on Sun, 4 Nov 2018 14:21:54 -0300)

> From: Dennis Mayr <dennis.mayr.c@gmail.com>
> Date: Sun, 4 Nov 2018 14:21:54 -0300
> 
> Emacs + Spacemacs user here.
> 
> Since this week, when opening a large Markdown file, Emacs crashes
> with segfault. At best, it freezes and does not respond to anything
> but to `killall emacs26` (asking to save desktop).
> 
> This is the file:
> https://pastebin.com/YZygPNTk
> 
> *gdb* result:
> 
> ```
> Thread 1 "emacs26" received signal SIGSEGV, Segmentation fault.
> 0x00000000005dbe78 in ?? ()
> ```
> 
> No backtrace available.

It doesn't crash here, ad without the backtrace it's hard to do
anything with this.

Can you try building the latest emacs-26 branch of the Emacs Git
repository, and see if the problem happens there as well?

Failing that, we'd need a backtrace to start looking into this.
Perhaps download and install debug data package for your Emacs
distribution, or build yourself without stripping the binary.  Then
repeat the recipe under GDB.

Thanks.





  reply	other threads:[~2018-11-04 18:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-04 17:21 bug#33257: 26.1; Emacs 26.1 crashes with SEGFAULT under markdown-mode while opening large file Dennis Mayr
2018-11-04 18:35 ` Eli Zaretskii [this message]
     [not found]   ` <CANpx60xFqG3C+H0vv5aS_ssZHx-54d7zFneT7JJvkt_0QVbTzA@mail.gmail.com>
     [not found]     ` <CANpx60wK=3E7jGye6OuZ5faS3ZreFDRhXBPw2DZrmL2wgQq6Pg@mail.gmail.com>
2018-11-05 15:41       ` Eli Zaretskii

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=835zxceln1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=33257@debbugs.gnu.org \
    --cc=dennis.mayr.c@gmail.com \
    /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).