unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
To: Eli Zaretskii <eliz@gnu.org>, Andrea Corallo <akrl@sdf.org>,
	Paul Eggert <eggert@cs.ucla.edu>
Cc: 57789@debbugs.gnu.org
Subject: bug#57789: Emacs 28.1 clone build with native compilation crashes on s390x
Date: Sat, 17 Sep 2022 16:00:17 -0500	[thread overview]
Message-ID: <87wna1k97i.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <83wna5yuws.fsf@gnu.org>


Eli Zaretskii <eliz@gnu.org> writes:

> Rob Browning <rlb@defaultvalue.org> writes:

> Does the build of the same code with the same options sans
> "--with-native-compilation" succeed, or does it also crash with
> similar symptoms?

Works fine.

> You can source it manually from the GDB prompt, when the segfault
> happens, and then invoke xbacktrace manually, can't you?

Yep.

  Breakpoint 1 at 0x2aa0004ef30: file emacs.c, line 400.
  Breakpoint 2 at 0x2aa0010f168: file xterm.c, line 10291.
  (gdb) xbacktrace
  "Automatic GC" (0x0)
  "internal-macroexpand-for-load" (0xffffa6a8)
  "eval-buffer" (0xffffaa28)
  "let" (0xffffac10)
  "let" (0xffffae28)
  "unwind-protect" (0xffffaff0)
  "let" (0xffffb1f8)
  "if" (0xffffb3c8)
  "load-with-code-conversion" (0xffffb650)
  "time-since" (0xffffbba8)
  "comp--native-compile" (0xffffbd38)
  "batch-native-compile" (0xffffbef0)
  "batch-byte+native-compile" (0xffffc080)
  "funcall" (0xffffc078)
  "if" (0xffffc268)
  "cond" (0xffffc438)
  "let*" (0xffffc618)
  "while" (0xffffc7e8)
  "let*" (0xffffc9c8)
  "progn" (0xffffcb98)
  "if" (0xffffccc0)
  "let" (0xffffceb8)
  "let" (0xffffd0b0)
  "command-line-1" (0xffffd280)
  "let" (0xffffd570)
  "command-line" (0xffffd740)
  "unwind-protect" (0xffffd9f0)
  "let" (0xffffdbe8)
  "if" (0xffffddb8)
  "normal-top-level" (0xffffdf88)

> Too bad, it means we have a heisenbug on our hands, which will make it
> even harder to debug (as if debugging crashes in GC were not hard
> enough already).
>
> What happens if you modify this variable:
>
>   (defcustom native-comp-debug (if (eq 'windows-nt system-type) 1 0)
>
> to have the value 1 or even zero, and then rebuild from scratch? does
> the build succeed then?

No, appears to crash in the same way.

> Yes, running the full test suite would be the logical next step.

Oh, I had run it, I just meant that I'd likely want to double-check via
testing in a loop to try to see if it might be an intermittent failure.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4





      parent reply	other threads:[~2022-09-17 21:00 UTC|newest]

Thread overview: 21+ 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
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 [this message]

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=87wna1k97i.fsf@trouble.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=57789@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@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).