bug#57789: Emacs 28.1 clone build with native compilation crashes on s390x

unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed

From: Stefan Kangas <stefankangas@gmail.com>
To: Rob Browning <rlb@defaultvalue.org>, Andrea Corallo <acorallo@gnu.org>
Cc: gerd.moellmann@gmail.com, 57789@debbugs.gnu.org,
	Eli Zaretskii <eliz@gnu.org>
Subject: bug#57789: Emacs 28.1 clone build with native compilation crashes on s390x
Date: Fri, 3 Jan 2025 12:59:24 -0600	[thread overview]
Message-ID: <CADwFkm=MOLq4Zm0geAmWJPJh5Jokqzcwn-FagkYQU0hamhOw=Q@mail.gmail.com> (raw)
In-Reply-To: <87r05jagqq.fsf@trouble.defaultvalue.org>

Rob Browning <rlb@defaultvalue.org> writes:

> In any case, I just tried both the current Debian package and an
> upstream emcs-29.4 checkout on zelenka.debian.org, and both fail.
>
> The emacs-29.4 tree fails like this:
>
> make[3]: Entering directory '/home/rlb/emacs/admin/unidata'
> make[3]: Nothing to be done for 'charscript.el'.
> make[3]: Leaving directory '/home/rlb/emacs/admin/unidata'
> make -C ../admin/unidata emoji-zwj.el
> make[3]: Entering directory '/home/rlb/emacs/admin/unidata'
> make[3]: Nothing to be done for 'emoji-zwj.el'.
> make[3]: Leaving directory '/home/rlb/emacs/admin/unidata'
>   ELC+ELN  ../lisp/emacs-lisp/eldoc.elc
>
> Error: wrong-type-argument ("../lisp/emacs-lisp/eldoc.el" hash-table-p [unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound unbound])
> Fatal error 11: Segmentation fault
> Backtrace:
> ../src/bootstrap-emacs(emacs_backtrace+0x46) [0x2aa1c2f12f6]
> ../src/bootstrap-emacs(terminate_due_to_signal+0x9e) [0x2aa1c18fb76]
> ../src/bootstrap-emacs(+0x8fdde) [0x2aa1c18fdde]
> ../src/bootstrap-emacs(+0x1ef45a) [0x2aa1c2ef45a]
> ../src/bootstrap-emacs(+0x1ef4a2) [0x2aa1c2ef4a2]
> linux-vdso64.so.1(__kernel_rt_sigreturn+0x0) [0x3ffdc0e5480]
> ../src/bootstrap-emacs(+0x2433a4) [0x2aa1c3433a4]
> ../src/bootstrap-emacs(visit_static_gc_roots+0x196) [0x2aa1c342dae]
> ../src/bootstrap-emacs(garbage_collect+0x1e6) [0x2aa1c3445d6]
> ../src/bootstrap-emacs(eval_sub+0x54c) [0x2aa1c370244]
> ../src/bootstrap-emacs(eval_sub+0x4ac) [0x2aa1c3701a4]
> ../src/bootstrap-emacs(Fcond+0x84) [0x2aa1c3711f4]
> ../src/bootstrap-emacs(eval_sub+0x8d2) [0x2aa1c3705ca]
> ../src/bootstrap-emacs(Fwhile+0x6e) [0x2aa1c370fb6]
> ../src/bootstrap-emacs(eval_sub+0x8d2) [0x2aa1c3705ca]
> ../src/bootstrap-emacs(Flet+0x2e2) [0x2aa1c374012]
> ../src/bootstrap-emacs(eval_sub+0x8d2) [0x2aa1c3705ca]
> ../src/bootstrap-emacs(Fcond+0x84) [0x2aa1c3711f4]
> ../src/bootstrap-emacs(eval_sub+0x8d2) [0x2aa1c3705ca]
> ../src/bootstrap-emacs(+0x271716) [0x2aa1c371716]
> ../src/bootstrap-emacs(+0x27362c) [0x2aa1c37362c]
> ../src/bootstrap-emacs(eval_sub+0x290) [0x2aa1c36ff88]
> ../src/bootstrap-emacs(Fsetq+0xa8) [0x2aa1c370ab0]
> ../src/bootstrap-emacs(eval_sub+0x8d2) [0x2aa1c3705ca]
> ../src/bootstrap-emacs(Fwhile+0x6e) [0x2aa1c370fb6]
> ../src/bootstrap-emacs(eval_sub+0x8d2) [0x2aa1c3705ca]
> ../src/bootstrap-emacs(Flet+0x2e2) [0x2aa1c374012]
> ../src/bootstrap-emacs(eval_sub+0x8d2) [0x2aa1c3705ca]
> ../src/bootstrap-emacs(Fcond+0x84) [0x2aa1c3711f4]
> ../src/bootstrap-emacs(eval_sub+0x8d2) [0x2aa1c3705ca]
> ../src/bootstrap-emacs(+0x271716) [0x2aa1c371716]
> ../src/bootstrap-emacs(+0x27362c) [0x2aa1c37362c]
> ../src/bootstrap-emacs(eval_sub+0x290) [0x2aa1c36ff88]
> ../src/bootstrap-emacs(Fsetq+0xa8) [0x2aa1c370ab0]
> ../src/bootstrap-emacs(eval_sub+0x8d2) [0x2aa1c3705ca]
> ../src/bootstrap-emacs(Fwhile+0x6e) [0x2aa1c370fb6]
> ../src/bootstrap-emacs(eval_sub+0x8d2) [0x2aa1c3705ca]
> ../src/bootstrap-emacs(Flet+0x2e2) [0x2aa1c374012]
> ../src/bootstrap-emacs(eval_sub+0x8d2) [0x2aa1c3705ca]
> ../src/bootstrap-emacs(Fcond+0x84) [0x2aa1c3711f4]
> ../src/bootstrap-emacs(eval_sub+0x8d2) [0x2aa1c3705ca]
> ...
> make[3]: *** [Makefile:282: ../lisp/emacs-lisp/eldoc.elc] Segmentation fault
> make[2]: *** [Makefile:841: ../lisp/emacs-lisp/eldoc.elc] Error 2
> make[2]: Leaving directory '/home/rlb/emacs/src'
> make[1]: *** [Makefile:544: src] Error 2
> make[1]: Leaving directory '/home/rlb/emacs'
> make[1]: Entering directory '/home/rlb/emacs'
> ***
> *** "make all" failed with exit status 2.
> ***
> *** You could try to:
> *** - run "make bootstrap", which might fix the problem
> *** - run "make V=1", which displays the full commands invoked by make,
> ***   to further investigate the problem
> ***
> make[1]: *** [Makefile:414: advice-on-failure] Error 2
> make[1]: Leaving directory '/home/rlb/emacs'
> make: *** [Makefile:370: all] Error 2
>
> Hope this helps

Thanks.

Could you run the crashing command under GDB, and when it segfaults,
produce the C-level and Lisp-level backtrace, and post them here?
There are instructions in DEBUG for how to do it.

Make sure to configure the build according to DEBUG, i.e. something like

  ./configure --enable-checking='yes,glyphs' --enable-check-lisp-object-type \
    CFLAGS='-O0 -g3'

next prev parent reply	other threads:[~2025-01-03 18:59 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14  1:04 bug#57789: Emacs 28.1 clone build with native compilation crashes on s390x Rob Browning
2022-09-14  2:42 ` Eli Zaretskii
2022-09-14  3:06   ` Rob Browning
2022-09-14  3:20     ` Rob Browning
2022-09-14 20:19   ` Rob Browning
2022-09-14 20:21     ` Rob Browning
2022-09-16  6:04       ` Gerd Möllmann
2022-09-17 21:04         ` Rob Browning
2022-09-18  5:22           ` Gerd Möllmann
2022-09-18  5:49             ` Eli Zaretskii
2022-09-18  5:55               ` Gerd Möllmann
2022-09-18  5:33           ` Eli Zaretskii
2022-09-24 21:06             ` Rob Browning
2023-06-07 21:15               ` Andrea Corallo
2023-09-11 18:08                 ` Stefan Kangas
2025-01-02  1:07                   ` Stefan Kangas
2025-01-02  3:40                     ` Rob Browning
2025-01-02  5:04                       ` Stefan Kangas
2025-01-03 18:34                         ` Rob Browning
2025-01-03 18:57                           ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-05 19:18                             ` Rob Browning
2025-01-07 13:51                               ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-08 10:37                                 ` Andrea Corallo
2025-01-03 18:59                           ` Stefan Kangas [this message]
2025-01-05 19:23                             ` Rob Browning
2022-09-15  7:10     ` Eli Zaretskii
2022-09-15 14:51       ` Paul Eggert via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-15 16:26         ` Rob Browning
2022-09-16  8:43         ` Andrea Corallo
2022-09-16  8:39       ` Andrea Corallo
2022-09-17 21:00       ` Rob Browning

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='CADwFkm=MOLq4Zm0geAmWJPJh5Jokqzcwn-FagkYQU0hamhOw=Q@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=57789@debbugs.gnu.org \
    --cc=acorallo@gnu.org \
    --cc=eliz@gnu.org \
    --cc=gerd.moellmann@gmail.com \
    --cc=rlb@defaultvalue.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).