-
Notifications
You must be signed in to change notification settings - Fork 2.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
ti.init() failed on CUDA backend and complained about an undefined symbol __stack_chk_fail #7523
Comments
This is a pretty weird behavior.. Is it on our CI bot? Could it be a driver issue? I have no problems with 495.29 with RTX3080. |
No, it’s my personal PC. I think some cuda-related pre-compiled library was compiled with -fstack-protector (by system package manager?), which is not understood by taichi's runtime. I was unable to reproduce this issue on Ubuntu 20.04 with lateset CUDA driver (525?) and RTX 2060s. It seems Arch Linux should take the blame for this:( |
Per offline discussion with @dream189free, this error only happens with Taichi compiled locally. @dream189free further verified that Taichi-nightly is out of problem on his local workstation. This issue shouldn't block v1.5.0 release since it's more related to the local compilation environment. |
Sorry for commenting on a closed issue, but I am trying to package taichi in nixpkgs, and I am having the same error when running I am not doing anything exotic really. |
Describe the bug
ti.init()
failed on CUDA backend and complainUndefined external symbol "__stack_chk_fail"
when using taichi built from source, (but it works well when using pre-built taichi 1.4.1 from pip).To Reproduce
Log/Screenshots
Additional comments
System info: Arch Linux with
The output of command
ti diagnose
The text was updated successfully, but these errors were encountered: