-
Notifications
You must be signed in to change notification settings - Fork 248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Random segfault for QEMU builds in GitHub Actions #2257
Comments
It's a bug in emulation. You can either pin the QEMU version, or better yet, use See #2256. I'll copy @joerick's answer here for posterity: I believe you're hitting a bug around setup-qemu-action. I didn't see it myself but @mayeut just pushed this fix to our repo- The referenced issues are docker/setup-qemu-action#188 and tonistiigi/binfmt#215. @mayeut's workaround is the following in a github workflow: - name: Set up QEMU
if: runner.os == 'Linux'
uses: docker/setup-qemu-action@v3
with:
# This should be temporary
# xref https://github.com/docker/setup-qemu-action/issues/188
# xref https://github.com/tonistiigi/binfmt/issues/215
image: tonistiigi/binfmt:qemu-v8.1.5 |
I missed it initially, but buried in the binfmt issue that was linked above there is discussion about the cause being related to building qemu with --disable-pie and aslr with the kernel the GHA runners ship (and qemu 8.1+ having a patch related to the segfault): tonistiigi/binfmt#215 (comment) |
Related? https://github.com/e-dant/watcher/actions/runs/13093964783/job/36534092020#step:4:511
|
See adafruit/Adafruit_Blinka_Raspberry_Pi5_rp1pio#3 and pypa/cibuildwheel#2257 for more background
@e-dant, that's the same issue: random segfaults with QEMU. |
avoid qemu bug pypa/cibuildwheel#2257
avoid qemu bug pypa/cibuildwheel#2257
avoid qemu bug pypa/cibuildwheel#2257
Using advice from pypa/cibuildwheel#2257
Using advice from pypa/cibuildwheel#2257
Using advice from pypa/cibuildwheel#2257
Using advice from pypa/cibuildwheel#2257
Using advice from pypa/cibuildwheel#2257
Description
This is not so much an issue of
cibuildwheel
(I think), except you should be aware of it.GCC builds segfault on the AArch64 musllinux 1.2, manylinux 2014 and manylinux 2.28.
I couldn't pin-point a possible GCC issue to it. But it is odd that it appears in a stable version.
Maybe: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118583
Haven't tested it yet though.
Feel free to close this if you see it as out of scope. But I wanted to drop it here in case people search for it in this context. Or others already found a solution.
Runs:
manylinux 2.28
https://github.com/capstone-engine/capstone/actions/runs/13012237284/job/36292511727?pr=2614
manylinux 2014
https://github.com/capstone-engine/capstone/actions/runs/13011576391/job/36290786445?pr=2614
musllinux 1.2
https://github.com/capstone-engine/capstone/actions/runs/13011576391/job/36290786852?pr=2614
Build log
No response
CI config
No response
The text was updated successfully, but these errors were encountered: