-
Notifications
You must be signed in to change notification settings - Fork 27
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 in sampling multi-processing code #308
Comments
Can you set the environment variable I’m looking for where the error happens in the OnUnload function. |
After the segfault, omnitrace repeatedly outputs
I don't know when it stops, so I kill omnitrace. |
any update on this? |
Is your library that is built against ROCm, |
yes. It's built on the same machine I do profiling, and there is only one ROCm version 5.7 on it, so I think it is. |
Given that looks like a python wheel and that ROCm 5.7 was just released recently, that might explain it. Omnitrace tends to encounter issues like this when there is a mismatch between the minor version of ROCm at runtime and the version it was built against. |
Thanks. I'll try again after you release Omnitrace pre-built for ROCm 5.7. |
This was likely fixed in #309 and/or using ROCm 5.7. Also, make sure you have |
I encounter a segfault when profiling a program with 2 process, each controlling 1 gpu. Here's the backtrace:
I once thought it might be the same cause with #304 , but the error message and backtrace are different, so I'm not sure.
The command I use is
omnitrace-sample python3 xxx.py
I'm using rocm 5.7 in ubuntu 22.04.
The text was updated successfully, but these errors were encountered: