From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Pip Cet via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#57789: Emacs 28.1 clone build with native compilation crashes on s390x Date: Tue, 07 Jan 2025 13:51:56 +0000 Message-ID: <871pxehguf.fsf@protonmail.com> References: <87h71aix5r.fsf@trouble.defaultvalue.org> <87y0ztc27x.fsf@trouble.defaultvalue.org> <87r05jagqq.fsf@trouble.defaultvalue.org> <877c7bk9ov.fsf@protonmail.com> <875xmt9ihs.fsf@trouble.defaultvalue.org> Reply-To: Pip Cet Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18403"; mail-complaints-to="usenet@ciao.gmane.io" Cc: gerd.moellmann@gmail.com, 57789@debbugs.gnu.org, Eli Zaretskii , Andrea Corallo , Stefan Kangas To: Rob Browning Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Jan 07 14:53:38 2025 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1tVA1X-0004bF-Ky for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 07 Jan 2025 14:53:35 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tVA15-0005Vp-GD; Tue, 07 Jan 2025 08:53:07 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tVA11-0005VH-AZ for bug-gnu-emacs@gnu.org; Tue, 07 Jan 2025 08:53:04 -0500 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1tVA11-0006S6-2B for bug-gnu-emacs@gnu.org; Tue, 07 Jan 2025 08:53:03 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debbugs.gnu.org; s=debbugs-gnu-org; h=MIME-Version:References:In-Reply-To:From:Date:To:Subject; bh=LWDwfZDLbI6YfcSOXOA1hU1qhAUQrYv9iaEppsJjFhg=; b=aQWv/HFvn7gMgtnkoIWwXeJow36A1y286mcyQcHneEqX7prnfNiX9geGI+yYlJSbViTjiH0TK+xYXP6SNIT8JysjzsK8Y1IGT9+5p4gG31Tx2u7ht6NaY7M6HMqLg3FlsJP9CDTyWAAzbx/UEFnkJFty0FJLc/vuEBDGKBjp5NiM3hn+J8i2ChXqrZQMMxg7/X7vr9vJOU3Fc3r2xYcX07+fNM6XUEx1/f7VnQ32gO7wiLjO208dB5vSlrR+dOoBRA4REHpUd/+ZwVw0lKzUzWKUUNEeuFkHR8j9Ya1I9z+hBIDrREPiFMsBeVXRgJFooFYF3zwFy6zFz4rb8bnq2w==; Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1tVA10-0000CP-G4 for bug-gnu-emacs@gnu.org; Tue, 07 Jan 2025 08:53:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Pip Cet Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 07 Jan 2025 13:53:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 57789 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 57789-submit@debbugs.gnu.org id=B57789.1736257933698 (code B ref 57789); Tue, 07 Jan 2025 13:53:02 +0000 Original-Received: (at 57789) by debbugs.gnu.org; 7 Jan 2025 13:52:13 +0000 Original-Received: from localhost ([127.0.0.1]:42140 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tVA0C-0000BC-JH for submit@debbugs.gnu.org; Tue, 07 Jan 2025 08:52:12 -0500 Original-Received: from mail-10628.protonmail.ch ([79.135.106.28]:37707) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1tVA0A-0000Av-Ht for 57789@debbugs.gnu.org; Tue, 07 Jan 2025 08:52:11 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1736257920; x=1736517120; bh=LWDwfZDLbI6YfcSOXOA1hU1qhAUQrYv9iaEppsJjFhg=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector:List-Unsubscribe:List-Unsubscribe-Post; b=vQDwfyVOEhbYTbG8gqcVUKNwxWE0ax0Dq2OXpkcTRrYE6icFVF5wk5SDUL23Xywmj 6hhf9/kAXzH5VbPIvmjOJdcgWYhFg+0YrEXJuS0bEydvoZhniPcg7motB1NmzZOCKw mgFr3FlQXw1PGZV1zgeLd9FNo3eGkoUxkcY2kF0Ewf/FQzLTqiLGbG/FwyRww3TAUB Vjo8hkfovUXsJSWA9XS0nsR4GNHjhYx9hAKm6tTb7VhbvoMvw/aFgCDmClAHQsfGg8 rCZiYkxkxtgk3tFluaWdR6BdnMAm6l2ca0rO1BlDZhw7P1+2Am1ybtCw7uIMhs22X8 7exCL4KAt8jew== In-Reply-To: <875xmt9ihs.fsf@trouble.defaultvalue.org> Feedback-ID: 112775352:user:proton X-Pm-Message-ID: dc56540300af1342e8144e9bb32f953ebb746cf8 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:298720 Archived-At: "Rob Browning" writes: > Pip Cet writes: > >> Same compiler? Is ASLR in use? > > Should be roughly the same compiler, both are building a "current" > unstable tree, and I build the one on zelenka a few days ago and the > mmdebstrap one the day before yesterday. Not sure offhand wrt ASLR. Hmm. Is there any way for you to share the binaries that don't work? It would be interesting to see whether the binary that crashes on silicon works in the emulator. >> In any case, I'm always interested in weird machines, even if they're >> virtual, so I'd appreciate such instructions. > > OK, so if you have access to a Debian host with recent enough versions > (fwiw, I was likely using trixie (testing) versions of debvm and > mmdebstrap), this should work. Thank you very much! The instructions worked for me! I could build Emacs, but, as expected, there was no crash. It's still possible that __builtin_unwind_init was buggy in one GCC version but not the other, but it does generate what looks like the right code here, which makes that possibility less likely. >> Can you disassemble the Fwhile, eval_sub, and visit_static_gc_roots >> functions? I assume s390 disassembled code isn't too hard to read... > > I'll plan to try that later, along with retrieving the requested > backtraces. If you can do so on a binary that doesn't work, mark_threads would also be an interesting function, since that's where __builtin_unwind is inlined. Pip