From: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
To: Emacs developers <emacs-devel@gnu.org>
Subject: Unexec dumping results in "Segmentation fault" on Windows Msys2
Date: Sat, 3 Apr 2021 23:20:17 +0300 [thread overview]
Message-ID: <e8d4551e-d3b2-7ffc-d8cd-d229582d72bc@gmail.com> (raw)
Hello. Whenever I try to build emacs-27 branch using msys2
--with-dumping=unexec I get:
make[2]: *** [Makefile:296:
/d/Emacs/source/repo/lisp/emacs-lisp/macroexp.elc] Segmentation fault
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [Makefile:296:
/d/Emacs/source/repo/lisp/emacs-lisp/byte-opt.elc] Segmentation fault
make[2]: *** [Makefile:296:
/d/Emacs/source/repo/lisp/emacs-lisp/autoload.elc] Segmentation fault
make[2]: *** [Makefile:296:
/d/Emacs/source/repo/lisp/emacs-lisp/cconv.elc] Segmentation fault
make[2]: *** [Makefile:296:
/d/Emacs/source/repo/lisp/emacs-lisp/bytecomp.elc] Segmentation fault
This only happens with the repository version. I've tried "make
extraclean" and other clean targets, they did not help.
With the source archive it's different in that Emacs compiles fine, but
it immediately crashes silently when you run it. That's actually the
other problem I'm trying to debug, since I'm trying to find a way to get
Emacs 26 to compile on Msys2 again and I'm observing the same
Segmentation faults for any unexec Emacs versions from the repo. So this
seems like a problem with some newer Msys2 package.
Could not test the master branch since trying to build it results in:
D:/Emacs/source/repo/src/pdumper.c: In function 'thaw_hash_tables':
D:/Emacs/source/repo/src/pdumper.c:5472:30: error: 'pdumper_hashes'
undeclared (first use in this function); did you mean 'pdumper_hook'?
5472 | Lisp_Object hash_tables = *pdumper_hashes;
| ^~~~~~~~~~~~~~
| pdumper_hook
next reply other threads:[~2021-04-03 20:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-03 20:20 Nikolay Kudryavtsev [this message]
2021-04-04 7:11 ` Unexec dumping results in "Segmentation fault" on Windows Msys2 Eli Zaretskii
2021-04-04 7:55 ` Eli Zaretskii
2021-04-04 8:41 ` Nikolay Kudryavtsev
2021-04-04 11:34 ` Eli Zaretskii
2021-04-14 22:11 ` Nikolay Kudryavtsev
2021-04-15 6:49 ` Eli Zaretskii
2021-04-15 13:07 ` Camm Maguire
2021-04-15 13:49 ` Eli Zaretskii
2021-04-15 15:47 ` Nikolay Kudryavtsev
2021-04-15 16:08 ` Eli Zaretskii
2021-04-15 19:17 ` Nikolay Kudryavtsev
2021-04-15 19:59 ` Eli Zaretskii
2021-04-16 16:57 ` Nikolay Kudryavtsev
2021-04-16 19:41 ` Eli Zaretskii
2021-04-21 16:33 ` Nikolay Kudryavtsev
2021-04-21 17:41 ` Eli Zaretskii
2021-04-21 18:19 ` Nikolay Kudryavtsev
2021-04-22 14:25 ` Eli Zaretskii
2021-04-29 19:17 ` Nikolay Kudryavtsev
2021-04-30 11:24 ` Eli Zaretskii
2021-05-02 9:43 ` Nikolay Kudryavtsev
2021-05-02 10:17 ` Eli Zaretskii
2021-04-22 17:22 ` Eli Zaretskii
2021-04-22 18:59 ` Nikolay Kudryavtsev
2021-04-22 19:13 ` Eli Zaretskii
2021-04-22 19:26 ` Nikolay Kudryavtsev
2021-04-16 7:45 ` Eli Zaretskii
2021-04-15 16:12 ` Eli Zaretskii
2021-04-15 19:45 ` Nikolay Kudryavtsev
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=e8d4551e-d3b2-7ffc-d8cd-d229582d72bc@gmail.com \
--to=nikolay.kudryavtsev@gmail.com \
--cc=emacs-devel@gnu.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).