Arnaud
Arnaud
I get the same error using the latest 4.1 ROCm release.
Tracing with '--sys-trace' alone works correctly.
I am not able to reproduce this issue with the latest ROCm (5.0.0).
This issue is still happening on ROCm 5.0.0.
well, I did a pull request, but other changes were needed so there was a pull request by paul #594.
Kind of, I had spoken about getting user to tracing with a tool that was already installed on most distros. ftrace was mentioned but that is all. Now that Trace...