my environment information are as follows:
driver version on Windows: 555.99
cuda version on Windows10: 12.5
nvcc version on Windows10: V12.5.40
WSL2 Ubuntu version: 20.04.6 LTS
nvcc version on WSL2: V12.5.40
cuda-gdb version on WSL2: 13.2
my HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\GPUDebugger\EnableInterface is set to 1.
No matter what CUDA program I run, once it reaches the kernel, it will report this error (If cuda-gdb is not applicable, it will run normally)
(cuda-gdb) n
[New Thread 0x7ffff6cd3000 (LWP 312)]
[New Thread 0x7ffff59c3000 (LWP 313)]
[Detaching after fork from child process 314]
[New Thread 0x7ffff4fb5000 (LWP 322)]
[Thread 0x7ffff4fb5000 (LWP 322) exited]
[New Thread 0x7ffff4fb5000 (LWP 323)]
[New Thread 0x7fffe1e12000 (LWP 324)]
Error: get_elf_image(0): Failed to read the ELF image handle 93825002597824 relocated 1, error=CUDBG_ERROR_INVALID_ARGS, error message=
I have uninstalled and reinstall the Driver and CUDA on Windows, and update both to the latest version.
I also have uninstalled and reinstalled the CUDA on WSL2, and update it to the latest version.
now, my environment information is as follows:
Windows 10 (professional edition) 64bit 22H2 19045.4412
CPU: Intel i5-12600KF
GPU: NVIDIA RTX 4060
Driver on Windows: 560.81
CUDA on Windows: 12.6, v12.6.20
WSL2: Ubuntu 20.04.6 LTS (GNU/Linux 5.10.16.3-microsoft-standard-WSL2 x86_64)
Driver on WSL2: 560.81 (shared with Windows)
CUDA on WSL2: 12.6, v12.6.20
cuda-gdb on WSL2: 13.2
gcc: 9.4.0
gdb: 9.2
python3: 3.8.10
HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\GPUDebugger\ EnableInterface is set to 1.
However, the latest version still has the same issue. Directly compiling and running are normal, only errors occur when using cuda-gdb.
The following figure shows the output obtained by compiling and running 'cuda-samples-12.4/1_Utilities/deviceQuery’ normally
I tried the simplest Hello World program and it worked fine when compiled and run directly. However, when checking with compute-sanitizer, errors were found, and when running with cuda-gdb, errors were also reported.
Hello, could you please provide us with detailed log by setting an environment variable named NVLOG_CONFIG_FILE pointing to the configuration file nvlog.config, running the app under the debugger and uploading the /tmp/debugger.log result.
Running compute-sanitizer will receive a prompt from “Error: Device not support.” (However, it appears that the GPU is still executing and receiving output “Hello world”)
After the elf error, can you run the debugger command info shared and post the output?
Also, can you check if hardware-accelerated GPU scheduling enabled on your system?
Can you post the env in which you run the app via the env command?
Does the ‘hardware-accelerated GPU scheduling’ refer to the following figure ‘硬件加速GPU计划’ on Windows?
This option has always been turned off, but the CUDA application on Windows and WSL2 can run normally without debugger.
I run the comman dxdiag.exe on Windows PowerShell, and output is as follows: (I have two screens, the main screen is 4K, and the other is 1080P)
I have saved all the information to ‘DxDiag.txt’ DxDiag.txt (106.3 KB)
Hi
my other PC is also running windows 10, and doesn’t have an NVIDIA GPU.
My current PC is mainly used for work, considering the stability of many other software, it is not suitable to upgrade to windows 11.
I’m sorry about this.