unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: NiwTinray <niwtrx@icloud.com>
Cc: 38912@debbugs.gnu.org
Subject: bug#38912: 27.0.60; PDumper meets segmentation fault when evil is loaded
Date: Sat, 04 Jan 2020 11:17:54 +0200	[thread overview]
Message-ID: <83ftgvh96l.fsf@gnu.org> (raw)
In-Reply-To: <333553AC-68DE-4F1C-9586-5A13248AD6DD@icloud.com> (bug-gnu-emacs@gnu.org)

> Date: Sat, 4 Jan 2020 09:49:14 +0800
> From: NiwTinray via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> I was testing the new portable dumper with my personal Emacs. When I
> loaded my dumped file, Emacs crashed on segmentation fault.
> After tracking down the issue, I found the issues is caused by the
> undo-tree mode in package "evil".
> To reproduce the bug, try this:
> 
> emacs --batch -f package-initialize --eval='(use-package evil :ensure
> t)' --eval='(dump-emacs-portable "test.pdmp")'  && emacs --dump-file
> test.pdmp

I cannot reproduce this from "emacs -Q" because 'use-package' is not a
known function.  Can you show a recipe starting from "emacs -Q",
please?

Also, does this happen if you add -Q to the Emacs invocation after
dumping?  If not, there's more detail missing in your report: the
customizations in your init files.

In addition, please also show the Lisp-level backtrace from the crash,
by using the xbacktrace command (it is defined in the src/.gdbinit
file in the Emacs source tree).

> Backtrace on crash:
> #0  0x00000000004f1240 in Fcurrent_active_maps (olp=olp@entry=0x30, position=position@entry=0x0) at keymap.c:1541

GDB usually displays the fatal signal that killed the program; can you
show that part as well?

Thanks.





  reply	other threads:[~2020-01-04  9:17 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-04  1:49 bug#38912: 27.0.60; PDumper meets segmentation fault when evil is loaded NiwTinray via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-01-04  9:17 ` Eli Zaretskii [this message]
     [not found]   ` <D1473DD8-48F8-4204-80B5-BE6396B8B668@icloud.com>
2020-01-05 18:45     ` Eli Zaretskii
2020-01-06 15:51       ` Pip Cet
2020-01-06 16:34         ` Eli Zaretskii
2020-01-06 16:38           ` Pip Cet
2020-01-06 17:20             ` Eli Zaretskii
2020-01-06 17:01           ` Daniel Colascione
2020-01-06 17:13             ` Pip Cet
2020-01-06 17:25             ` Eli Zaretskii
     [not found]             ` <CAOqdjBfekLB8ZaDOA3Zys5u83KkSQnb51ZcM0FVSXrcv9ZDeBQ@mail.gmail.com>
2020-01-06 17:30               ` Eli Zaretskii
2020-01-06 18:13                 ` Stefan Monnier
2020-01-06 18:19                   ` Noam Postavsky
2020-01-06 18:29                   ` Eli Zaretskii
2020-01-07 19:31                   ` Pip Cet
2020-01-07 20:03                     ` Stefan Monnier
2020-01-07  2:38               ` Paul Eggert
2020-01-07  3:34                 ` dancol
2020-01-07 14:16                   ` Stefan Monnier
     [not found]                   ` <jwvv9pnz76y.fsf-monnier+emacs@gnu.org>
2020-01-07 19:32                     ` Paul Eggert
2020-01-07 15:47                 ` Eli Zaretskii
2020-01-07 17:37                   ` Stefan Monnier
     [not found]                   ` <jwv8smjxj7d.fsf-monnier+emacs@gnu.org>
2020-01-07 17:43                     ` Eli Zaretskii
     [not found]                     ` <8336crcgd0.fsf@gnu.org>
2020-01-07 18:01                       ` Stefan Monnier
     [not found]                       ` <jwvwoa3w3lb.fsf-monnier+emacs@gnu.org>
2020-01-07 18:11                         ` Eli Zaretskii
2020-01-07 18:47                           ` Stefan Monnier
2020-01-07 18:29                         ` martin rudalics
     [not found]                         ` <1e33c53e-f6ae-a3bf-6ce0-5c1894cb9b35@gmx.at>
2020-01-07 18:43                           ` Stefan Monnier
     [not found]                           ` <jwvftgrw1k1.fsf-monnier+emacs@gnu.org>
2020-01-07 18:58                             ` martin rudalics
2020-01-07 23:43             ` Richard Stallman
2020-01-06 17:10       ` Daniel Colascione
2020-03-05  7:14         ` Eli Zaretskii
2020-03-09  2:15           ` Daniel Colascione
2020-03-09  3:26             ` Eli Zaretskii
2021-06-24 16:30               ` bug#32503: 26.1; Byte-compiled functions don't hash consistently Lars Ingebrigtsen
2022-04-28 11:41                 ` bug#38912: 27.0.60; PDumper meets segmentation fault when evil is loaded Lars Ingebrigtsen

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=83ftgvh96l.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=38912@debbugs.gnu.org \
    --cc=niwtrx@icloud.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).