Hi is here anyone who knows if the hardware watchpoint in cuda-gdb can actually work or not? I tried to use it to watch a shared mem variable, but it never stops even if I find the value of that variable has changed. Thanks!
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Creating a watchpoint in debugger (gdb, totalview) will crash TX1 system | 2 | 647 | October 18, 2021 | |
| Still cannot properly watch variables in CUDA kernels | 27 | 3964 | February 23, 2021 | |
| cuda-gdb don't stop the program | 1 | 1523 | January 24, 2020 | |
| Cuda-gdb doesn't print correct value that a pointer point to within the kernel | 5 | 1502 | March 15, 2022 | |
| cuda-gdb can't examine device memory? | 2 | 2447 | November 25, 2010 | |
| About the CUDA-GDB category | 1 | 1910 | February 29, 2024 | |
| CUDA Warp Watch window buggy | 0 | 454 | November 8, 2020 | |
| Nsight skips (ignores) over break points in VS10 Cuda works fine, nsight consistently skips over sev | 6 | 2891 | June 1, 2012 | |
| CUDA-GDB to debug Python TensorFlow scripts | 2 | 1369 | October 28, 2021 | |
| Dump/inspect NVIDIA GPU global memory contents corresponding to arbitrary (but not invalid) addresses | 3 | 428 | November 8, 2024 |