I am trying to debug a memory access problem using cuda-memcheck. The out of bounds read provides an address and a source code line number, but that line number in the kernel is no where near the actual error. Are there some issues or restrictions concerning line numbering. These source files have a large number of #ifdef - #endif regions which are NOT compiled into the version I am trying to debug. Do those somehow affect the line numbering in memcheck. Runnign cuda 4.0 on linux redhat 5
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| cuda-memcheck shows memory out of bound error in a kernl with large number of if else condition in k | 4 | 971 | June 6, 2014 | |
| cuda-memcheck oddity -- reporting wrong source location for an invalid write! Line number report | 2 | 5228 | October 19, 2011 | |
| cuda-memcheck error: Address is out of bounds. | 2 | 5773 | November 12, 2012 | |
| Bug in cuda-memcheck? | 2 | 1415 | March 14, 2013 | |
| hardware breakpoint or something :) | 2 | 1380 | September 14, 2008 | |
| Cuda-memcheck can't report the invalid write | 3 | 541 | June 8, 2023 | |
| Tracking Invalid read size and illegal memory access | 3 | 7682 | May 24, 2016 | |
| Strange access to memory | 4 | 583 | March 17, 2014 | |
| cuda-memcheck with CUDA Fortran? | 0 | 3620 | February 18, 2011 | |
| printf in CUDA | 0 | 4829 | December 22, 2009 |