-
-
Notifications
You must be signed in to change notification settings - Fork 237
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
steamcmd failed with "Fatal error: futex robust_list not initialized by pthreads" #1034
Comments
This error "Fatal error: futex robust_list not initialized by pthreads" is a steam error when the mutex don't have the expected glibc behaviour. |
My host uses the ubuntu 22.04 image provided by Orangepi, and the docker container uses the official ubuntu 20.04 image of arm64/v8 platform. Can this error be resolved by adding some dependencies? |
Not really. It's steam checking if an offset in some inner syscall structure is the expected value... |
What should I do to enable box32 option of box64? I didn't find it in box64/docs/compile.md. And how to configure binfmts for box32 in the docker container after installing? |
Mmm, indeed, I need to add some hint there on how to add box32. You can use |
I've added the box32 option and removed box86, but a new error Segmentation fault appears
When I run steamcmd repeatedly, Segmentation fault increases |
I don't reproduce the issue on my side It just update and start correctly. The segfault you pasted doesn't make sense to me: RSP is correct, the opcode is a |
I ran a new docker container, reinstalled box64, box32 and steamcmd ,add run with BOX64_SHOWBT=1, nothing seemed to have changed.
|
I still don't understand what could be happening there... Can run steamcmd with gdb? and do "bt" when the segfault happens? |
@ptitSeb here you go
|
Update: using box86 v0.3.6 prevents this error. There is a new error which is probably a path issue:
|
I installed pre-build packages of box86 and box64 in the arm64v8 ubuntu docker container and configured binfmts by following this link.
logs.txt
The text was updated successfully, but these errors were encountered: