I think I found a bug in the new Cuda Hardware Debugger cuda-gdb. I was examining an unsigned char array on the device that resides in global memory space. When I used ‘print arrayname’, all entries of the array where listed correctly. Then I used ‘set arrayname = y’ for some fields and afterwards printed the complete array again. All changes where done properly. But when I used ‘print arrayname’ the wrong entries were printed. Every fourth entrie is correct, the rest seems to be shifted. Perhaps the bytes are read in the wrong direction or something like this.
The system I encountered this problem:
SuSe 11.1 64Bit
2 * Dual Core AMD Opteron™ Processor 270 (2GHz)
GeForce GTX 280