From: Rob Browning <rlb@defaultvalue.org>
To: Stefan Kangas <stefankangas@gmail.com>,
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: Sun, 05 Jan 2025 13:23:17 -0600 [thread overview]
Message-ID: <871pxh9iai.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <CADwFkm=MOLq4Zm0geAmWJPJh5Jokqzcwn-FagkYQU0hamhOw=Q@mail.gmail.com>
Stefan Kangas <stefankangas@gmail.com> writes:
> 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.
I haven't gotten to that yet, but when starting to look in to it I
wondered about the optimization level, and after some testing found that
-O2 crashes while -O1 and -O0 do not.
--
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
next prev parent reply other threads:[~2025-01-05 19:23 UTC|newest]
Thread overview: 30+ 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-03 18:59 ` Stefan Kangas
2025-01-05 19:23 ` Rob Browning [this message]
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=871pxh9iai.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=57789@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=eliz@gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=stefankangas@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 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).