Osrt tracing error on Xavier

The following error only happens on Xavier using nsys CLI when --trace includes osrt (including the default set of options when --trace isn’t specified):

**** Analysis failed with:
Status: TargetProfilingFailed
Props {
  Items {
    Type: DeviceId
    Value: "Local (CLI)"
  }
}
Error {
  Type: RuntimeError
  SubError {
    Type: ProcessEventsError
    Props {
      Items {
        Type: ErrorText
        Value: "/build/agent/work/20a3cfcd1c25021d/QuadD/Host/Analysis/Modules/TraceProcessEvent.cpp(240): Throw in function const char* {anonymous}::GetOSRuntimeNameFromId(const DevicePtr&, uint64_t)\nDynamic exception type: boost::exception_detail::clone_impl<QuadDCommon::InvalidArgumentException>\nstd::exception::what: InvalidArgumentException\n[QuadDCommon::tag_error_text*] = Target does not support OS runtime libraries trace.\n"
      }
    }
  }
}

Hello, jhurliman!

You application or one of its dependencies is using “syscall” with “SYS_futex” which is triggering this bug in Nsight Systems. This is a known issue that was fixed. There is unfortunately no workaround for the version of Nsight Systems you are using so you only have three options:

  1. If possible, use the POSIX thread API instead of calling “syscall”
  2. Explicitly disable “osrt” tracing when using the CLI or GUI
  3. Wait for the next JetPack release

@afroger the next version of JetPack has been released, do you know if this issue was fixed?