From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15491] New: segmentation fault in busybox/glibc due to CONFIG_STACK_OPTIMIZATION_386
Date: Sat, 25 Mar 2023 21:10:12 +0000 [thread overview]
Message-ID: <bug-15491-163@https.bugs.busybox.net/> (raw)
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
next reply other threads:[~2023-03-25 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 21:10 bugzilla [this message]
2023-03-25 21:12 ` [Buildroot] [Bug 15491] segmentation fault in busybox/glibc due to CONFIG_STACK_OPTIMIZATION_386 bugzilla
2023-03-26 12:15 ` bugzilla
2024-06-15 15:07 ` bugzilla
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-15491-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox