all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Compro Prasad <comproprasad@gmail.com>
Cc: 34206@debbugs.gnu.org
Subject: bug#34206: Pdumper giving a segfault
Date: Sat, 26 Jan 2019 10:06:26 +0200	[thread overview]
Message-ID: <83munn6dx9.fsf@gnu.org> (raw)
In-Reply-To: <CAF5vbPn8KOW=H6w0WUSaAs5fdFsGM2X4s8jV-ureVxePRkMr8w@mail.gmail.com> (message from Compro Prasad on Sat, 26 Jan 2019 12:03:59 +0530)

> From: Compro Prasad <comproprasad@gmail.com>
> Date: Sat, 26 Jan 2019 12:03:59 +0530
> 
> Emacs source: official master branch (commit: 7960951d5d)
> Emacs config: https://github.com/Compro-Prasad/spacemacs/tree/pdumper-is-in-master
> (commit: f5eef2127ad4d)
> Spacemacs config: https://github.com/Compro-Prasad/.spacemacs.d
> (commit: 8a1eebc65f9a)
> 
> Build command: ./configure --enable-checking='yes,glyphs'
> --enable-check-lisp-object-type CFLAGS='-O0 -g3' --with-xwidgets &&
> make -j2
> 
> GDB log: https://pastebin.com/2uMPHCRV

This seems to indicate your configuration is quite complex, and I
cannot easily understand what are you doing that is different from
the normal build and "emacs -Q" to start Emacs.  In particular, this:

  $ gdb ./src/emacs-27.0.50.11
  Reading symbols from ./src/emacs-27.0.50.11...done.
  (gdb) r --dump-file="/home/compro/.emacs.d/.cache/dumps/spacemacs.pdmp"
  Starting program: /home/compro/Downloads/git.savannah.gnu.org/git/emacs/src/emacs-27.0.50.11 --dump-file="/home/compro/.emacs.d/.cache/dumps/spacemacs.pdmp"

indicates that your pdump file is spacemacs.pdmp, but I don't know how
that file was produced, and I cannot easily understand what is
different in your build procedure from the normal upstream build of
Emacs.

Maybe you should first take this up with then maintainers of the
Compro-Prasad/spacemacs package.

> OS: Antergos(Arch Linux)
> Compiler: gcc version 8.2.1 20181127 (GCC)
> 
> Can't provide further information because Emacs segfaults before it
> can load any elisp packages while loading the dump file.

The backtrace indicates that it segfaults _after_ loading the dump
file, inside the call to init_buffer.

> I might be doing something wrong here. Can you please guide me how to
> use the pdumper in Emacs or what info topic is it under?

There's no difference in how pdump'ed Emacs should be used, it's the
same as you'd use an unexec'ed Emacs.

I suggest to file an issue with the maintainers of
Compro-Prasad/spacemacs.





  reply	other threads:[~2019-01-26  8:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-26  6:33 bug#34206: Pdumper giving a segfault Compro Prasad
2019-01-26  8:06 ` Eli Zaretskii [this message]
2019-01-26  8:22   ` Eli Zaretskii
2019-01-26  9:03   ` Compro Prasad
2019-01-26 10:49     ` Eli Zaretskii
2019-01-26 15:05       ` Compro Prasad
2019-01-26 15:18         ` Eli Zaretskii
2019-01-27  3:50       ` Daniel Colascione
2019-01-27  3:52 ` Daniel Colascione
2019-01-28 12:19   ` Compro Prasad

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83munn6dx9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=34206@debbugs.gnu.org \
    --cc=comproprasad@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.