Wsl2 cuda-gdb is attached to a python process for debugging, and it gets stuck on certain code

[waitting33]

cuda-toolkit version 12.3
Ubuntu 18
WSL2

I refer to this tutorial to debug my python files

Debugger for python & C/C++ CUDA

Its possible to use cuda-gdb from python, assuming you only need to debug the C/C++ portion. I don’t know of a debugger that can jump from debugging python to debugging CUDA C++ To debug a CUDA C/C++ library function called from python, the following is one possibility, inspired from this article For this walk through, I will use the t383.py and t383.cu files verbatim from this answer: https://stackoverflow.com/a/45524623/1695960 I’ll be using CUDA 10, python 2.7.5, on CentOS7 Compile yo…

Here is my test python file.(It didn’t call the .cu file,just for test)

import torch
b=[[4,5,6],[7,8,9]]
b=torch.tensor(b)
print("arrive here 11")
b=b.cuda()
print("arrive here 22")
print(b)
print(torch.unsqueeze(b,2).shape)

In step seven,my python process is blocked when executing b=b.cuda().
What should I do to fix it? Looking forward to your reply

[veraj]

Hi, @waitting33
This seems duplicate with another topic you post Wsl2 cuda-gdb is attached to a python process for debugging, and it gets stuck on certain code

I am going to close this. Thanks !
Any disagree, please let me know.