From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 40970C6FD1C for ; Sat, 25 Mar 2023 21:11:14 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id E91588207B; Sat, 25 Mar 2023 21:11:13 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org E91588207B X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hs7FqUmfIARc; Sat, 25 Mar 2023 21:11:13 +0000 (UTC) Received: from ash.osuosl.org (ash.osuosl.org [140.211.166.34]) by smtp1.osuosl.org (Postfix) with ESMTP id 3E1D581FFB; Sat, 25 Mar 2023 21:11:12 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 3E1D581FFB Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136]) by ash.osuosl.org (Postfix) with ESMTP id 8AEF71BF39A for ; Sat, 25 Mar 2023 21:10:13 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id 717D060A9B for ; Sat, 25 Mar 2023 21:10:13 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 717D060A9B X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp3.osuosl.org ([127.0.0.1]) by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x-rFb_b5rKer for ; Sat, 25 Mar 2023 21:10:12 +0000 (UTC) Received: from busybox.osuosl.org (busybox.osuosl.org [140.211.167.122]) by smtp3.osuosl.org (Postfix) with ESMTP id B5261607B4 for ; Sat, 25 Mar 2023 21:10:12 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org B5261607B4 Received: by busybox.osuosl.org (Postfix, from userid 81) id A0688820FD; Sat, 25 Mar 2023 21:10:12 +0000 (UTC) From: bugzilla@busybox.net To: buildroot@uclibc.org Date: Sat, 25 Mar 2023 21:10:12 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: buildroot X-Bugzilla-Component: Other X-Bugzilla-Version: 2023.02 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fesc2000@mailbox.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P5 X-Bugzilla-Assigned-To: unassigned@buildroot.uclibc.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc target_milestone Message-ID: X-Bugzilla-URL: https://bugs.busybox.net/ Auto-Submitted: auto-generated MIME-Version: 1.0 Subject: [Buildroot] [Bug 15491] New: segmentation fault in busybox/glibc due to CONFIG_STACK_OPTIMIZATION_386 X-BeenThere: buildroot@buildroot.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion and development of buildroot List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: buildroot-bounces@buildroot.org Sender: "buildroot" https://bugs.busybox.net/show_bug.cgi?id=15491 Bug ID: 15491 Summary: segmentation fault in busybox/glibc due to CONFIG_STACK_OPTIMIZATION_386 Product: buildroot Version: 2023.02 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component: Other Assignee: unassigned@buildroot.uclibc.org Reporter: fesc2000@mailbox.org CC: buildroot@uclibc.org Target Milestone: --- Hi, i was facing the issue that busybox (ls appled) was generating a random segmentation fault in libc/ctime() (i386 platform, glibc 2.30). The actual problem was that CONFIG_STACK_OPTIMIZATION_386 was set by default, causing an 8 byte aligned stack, and glibc uses a movaps instruction on it (which requires 16 byte alignment). Obviously i could solve this by disabling CONFIG_STACK_OPTIMIZATION_386, but it took me quite a while to find it out. This really should be disabled by default. After some digging it seems that the ABI nowadays mandates 16 byte stack alignment even for i386 (see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38496). -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot