-
-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
s390x statically linked binaries terminate with segmentation fault #306473
Comments
Building using musl until NixOS/nixpkgs#306473 is resolved. Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
Building using musl until NixOS/nixpkgs#306473 is resolved. Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
Building using musl until NixOS/nixpkgs#306473 is resolved. Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
Building using musl until NixOS/nixpkgs#306473 is resolved. Refers to cri-o/cri-o#7911 Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
Building using musl until NixOS/nixpkgs#306473 is resolved. Refers to cri-o/cri-o#7911 Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
Building using musl until NixOS/nixpkgs#306473 is resolved. Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
Building using musl until NixOS/nixpkgs#306473 is resolved. Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
Building using musl until NixOS/nixpkgs#306473 is resolved. Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
Can you perhaps compile everything with debug symbols and get a backtrace? May help to identify the cause. That being said, I'm pretty sure that s390 isn't a supported architecture here. Would you mind trying to reproduce the issue with a different glibc package? A quick google search shows that there seem to be Fedora RPMs: https://rpmfind.net/linux/rpm2html/search.php?query=glibc(s390-64) |
Building using musl until NixOS/nixpkgs#306473 is resolved. Refers to cri-o/cri-o#7911 Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
Building using musl until NixOS/nixpkgs#306473 is resolved. Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
Building using musl until NixOS/nixpkgs#306473 is resolved. Refers to cri-o/cri-o#7911 Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
Building using musl until NixOS/nixpkgs#306473 is resolved. Refers to cri-o/cri-o#7911 Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
Building using musl until NixOS/nixpkgs#306473 is resolved. Refers to cri-o/cri-o#7911 Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
Describe the bug
Statically linked binaries using
glibc.static
exit withterminated by signal SIGSEGV (Address boundary error)
.Steps To Reproduce
Steps to reproduce the behavior using the demo project in https://github.com/saschagrunert/s390x-nix:
When removing the
CFLAGS ?= -static
in theMakefile
, then it runs successfully:It also works when using
s390x-unknown-linux-musl
.Expected behavior
That the statically linked binaries don't segfault.
Screenshots
None
Additional context
None
Notify maintainers
@Ma27 @ConnorBaker @edolstra
Add a 👍 reaction to issues you find important.
The text was updated successfully, but these errors were encountered: