unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <akrl@sdf.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 57789@debbugs.gnu.org, Paul Eggert <eggert@cs.ucla.edu>,
	Rob Browning <rlb@defaultvalue.org>
Subject: bug#57789: Emacs 28.1 clone build with native compilation crashes on s390x
Date: Fri, 16 Sep 2022 08:39:35 +0000	[thread overview]
Message-ID: <xjfzgezbtmg.fsf@ma.sdf.org> (raw)
In-Reply-To: <83wna5yuws.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 15 Sep 2022 10:10:59 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Rob Browning <rlb@defaultvalue.org>
>> Cc: 57789@debbugs.gnu.org
>> Date: Wed, 14 Sep 2022 15:19:24 -0500
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> > Please run the crashing command under GDB, and when it segfaults,
>> > produce the C-level and Lisp-level backtrace, and post them here.
>> 
>> Starting from scratch with the emacs-28.1 commit I can reproduce the
>> failure when building via
>> 
>>   ./configure --prefix=/home/rlb/opt/emacs-tmp --with-native-compilation
>> 
>> It crashes with the same segfault repeatably, i.e. if you run make
>> again, it crashes again on the previously mentioned "... -l comp -f
>> batch-byte+native-compile international/titdic-cnv.el" invocation.  That
>> crash output is attached below.
>> 
>> After adjusting the Makefile.in invocation so I could run it with gdb in
>> exactly the same environment once it's failing on that command, I
>> captured the backtrace and included it below.
>
> Thanks.  The backtrace indicates that the crash is in GC.  This
> probably means we have some fundamental problem on that architecture.
> Andrea, any advice for how to investigate?

Mmmh one cheap way to maybe gather more info is to have a run under
valgrind.

Other than that I typically start debugging with GDB and possibly
rr. Like what is (or was) the object the GC is crashing on?  Why?
What's the last piece of code that touched it? Why?  IIUC here we have
no debug symbols so this makes it very difficult.

BTW the fact that -g has an impact on the crash is very odd

  Andrea






  parent reply	other threads:[~2022-09-16  8:39 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 [this message]
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=xjfzgezbtmg.fsf@ma.sdf.org \
    --to=akrl@sdf.org \
    --cc=57789@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --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).