Skip to content
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

Segmentation fault on opening a project on musl libc #21282

Closed
ronchaine opened this issue Aug 22, 2018 · 5 comments
Closed

Segmentation fault on opening a project on musl libc #21282

ronchaine opened this issue Aug 22, 2018 · 5 comments

Comments

@ronchaine
Copy link
Contributor

Godot version:
master branch, haven't found a working version yet

OS/device including version:
Any linux distribution using musl libc. Repeatable at least on Gentoo and Alpine.

  • amdgpu open source driver

Issue description:
When opening editor, godot crashes. Segmentation fault is visible in the debugger.

Steps to reproduce:

  • Have a linux that uses musl instead of glibc.
  • Launch godot, select any project, press "edit".

This might be amdgpu issue, or have something to do with musl stack size. Needs more data when it appears, and if it happens on non-amdgpu-systems.

@ronchaine
Copy link
Contributor Author

I am working on this myself, but unfortunately can't allocate much time. It's probably not very high priority anyways, since same computer can run godot just fine in glibc chroot.

@akien-mga
Copy link
Member

Can you get a backtrace?

@ronchaine
Copy link
Contributor Author

ronchaine commented Aug 25, 2018

#0  0x00007ffff7dc7c35 in memcpy () from /lib/ld-musl-x86_64.so.1
#1  0x00007ffff65fc704 in ?? () from /lib/libz.so.1
#2  0x00007ffff65fc989 in ?? () from /lib/libz.so.1
#3  0x00007ffff65fdeed in deflate () from /lib/libz.so.1
#4  0x00007ffff2c2d649 in ?? () from /usr/lib/dri/radeonsi_dri.so
#5  0x00007ffff2c2d8b5 in ?? () from /usr/lib/dri/radeonsi_dri.so
#6  0x00007ffff2c34991 in ?? () from /usr/lib/dri/radeonsi_dri.so
#7  0x00007ffff2c34727 in ?? () from /usr/lib/dri/radeonsi_dri.so
#8  0x00007ffff7dbbc2e in ?? () from /lib/ld-musl-x86_64.so.1
#9  0x0000000000000000 in ?? ()

I had the plan that I'd build mesa with debug symbols and take a closer look at that next, but haven't gotten to that yet. Don't know where that 0x0 comes though.

Also, sorry for late reply.

@ronchaine
Copy link
Contributor Author

OK, this is fixed by increasing stack size. There's a mesa patch for Void linux, and a PR exists for gentoo/musl and alpine that increases thread stack size. Closing this.

@rofl0r
Copy link

rofl0r commented Feb 9, 2019

i suppose this was the patch fixing it: void-linux/void-packages@18838a6 (linking it here in case others encounter this too).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants