Scheduler-locking option in cuda-gdb

Developer Tools CUDA Developer Tools CUDA-GDB
1

Hi,
There is one bullet in cuda-gdb document section B.Know Issues:
" * The scheduler-locking option cannot be set to on ."
According to gdb document (All-Stop Mode (Debugging with GDB)), scheduling-locking = on means other threads wouldn’t move when the current thread takes single-step. This bullet seems cuda-gdb can’t lock others threads (warps) during current warp is single-stepping. However, the experiment shows other warps indeed don’t move when current warp is doing single-step.
Is there anything I missed, or this document is out of date?

thanks.

2

Hi Yvlamg,
Thank you very much for your question. This is an expected behavior in current CUDA-GDB version: the scheduler-locking option only applies to CPU threads, so it’s not affecting the GPU threads (warps).

Hope this would help to clarify the issue. Please let me know if you need any additional information regarding this subject.