Nicolas Miller

@hdelan both of the patches are merged is this resolved now?

Perfect, thanks! Closing this now as we believe this is resolved, @alexbatashev feel free to re-open if the issue persists.

Note: this has been resolved for CUDA and HIP, but there are still some segfaults for Level Zero and Native CPU

> > Speaking of #1070, doesn't that fix this same issue? > > I don't see it setting `XPTI_ENABLE_INSTRUMENTATION` (but that's a minor issue), and I'm not really a big...

Looks like this is causing some build issues in the [L0 static build](https://github.com/oneapi-src/unified-runtime/actions/runs/11442371988/job/31832583777?pr=1811) Amongst other undefined symbols: ``` [ 56%] Building CXX object test/conformance/context/CMakeFiles/test-context.dir/__/source/environment.cpp.o /usr/bin/ld: ../../../lib/libur_adapter_level_zero.a(ur_interface_loader.cpp.o): in function `ur::level_zero::urGetTensorMapExpProcAddrTable(ur_api_version_t, ur_tensor_map_exp_dditable_t*)':...

ping @oneapi-src/unified-runtime-native-cpu-write @oneapi-src/unified-runtime-opencl-write @oneapi-src/unified-runtime-hip-write @oneapi-src/unified-runtime-level-zero-write This should be ready to review

> The fact this only adds support for CUDA may also be a sticking point. Currently as far as I'm aware no other target has this so this is purely...

The only test failures seem to be a problem with the runner: ``` urDevicesGet() failed to get number of devices. ```