From: Daniel Colascione <dancol@dancol.org>
To: Compro Prasad <comproprasad@gmail.com>, 34206@debbugs.gnu.org
Subject: bug#34206: Pdumper giving a segfault
Date: Sat, 26 Jan 2019 19:52:26 -0800 [thread overview]
Message-ID: <ca84aa82-2ab5-8c92-5683-50d1e1c2b705@dancol.org> (raw)
In-Reply-To: <CAF5vbPn8KOW=H6w0WUSaAs5fdFsGM2X4s8jV-ureVxePRkMr8w@mail.gmail.com>
On 1/25/19 10:33 PM, Compro Prasad wrote:
> 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
>
> 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.
>
> 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?
That looks like a legitimate bug. I don't know anything about spacemacs.
Can you provide a recipe for reproducing this crash starting from a
stock master checkout? Thanks.
next prev parent reply other threads:[~2019-01-27 3:52 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
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 [this message]
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=ca84aa82-2ab5-8c92-5683-50d1e1c2b705@dancol.org \
--to=dancol@dancol.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.