-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
tokio runtime could not be created #4220
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
Comments
The error message from valgrind says you should report the bug to them. |
It is also crashing when I don't use valgrind, see the core dump. So valgrind isn't the real cause. |
It says that it failed with |
(I have tested it locally using another cross-testing tool, it seems to work fine with -crt-static.) |
@taiki-e I tried this flag. This produces a dynamic linked library with this flag, for some reason I want a static one. The raspberry pi 4 can also run in 64bit mode as aarch64. I compiled my program for this target and run the raspberry pi in 64bit and the start behaviour was the same. So I think 32bit cause not the problem. @Darksonn I create a new repo which hopefully met what you wrote. And did also some tests, the results you can find in the Readme. |
Since it fails only with |
@taiki-e You are right, rust-musl-cross uses the latest version of @Darksonn @taiki-e Thanks for helping / pointing me to the right direction. |
I have a project where I use arm actix(tokio) musl mimalloc. When I run it on the raspberry I can see a error message in the title with running under valgrind.
I am not sure what cause the real problem.
A arm-musl-mimalloc-actix repo is available for reproduce the error and
everything is explained in more detail.
I start rust programming a view month ago, so my experience isn't very deep. Hope somebody can help me or point me to the right direction.
The text was updated successfully, but these errors were encountered: