Attach failed due to the internal driver error 0x414300000002e with cuda-gdb

odyssey471
Fri, 31 Oct 2025 02:53:28 +0000
CUDA-GDB

On a Linux server, when I try to attach a running process with cuda-gdb, I would receive such an error after lots of reading symbol from a .so lines.

But the cuda-gdb seems attached to the target process, however it losed all things as a CUDA gdb instead of a vanilla gdb. I can’t inspect anything related to CUDA, but I can still look into CPU-side things like threads, as the following figure shown.

And this error only appears when attach to a running process. If I run a process with cuda-gdb,

cuda-gdb python myscript.py

then it just works and I could inspect things like cuda contexts.

Info about my server:

OS: Ubuntu 20.04

Kernel: Linux 5.4.0-169-generic

Driver version: 545.23.08

Device: NVIDIA H100

If any additional information is required for diagnosing, please let me know, thanks in advance!

9 posts - 3 participants