cuda-gdb

cuda-gdb Error message

那年仲夏 提交于 2019-12-02 12:24:48
I tried to debug my CUDA application with cuda-gdb but got some weird error. I set option -g -G -O0 to build my application. I could run my program without cuda-gdb, but didn't get correct result. Hence I decided to use cuda-gdb, however, I got following error message while running program with cuda-gdb Error: Failed to read the valid warps mask (dev=1, sm=0, error=16). What does it means? Why sm=0 and what's the meaning of error=16 ? Update 1 : I tried to use cuda-gdb to CUDA samples, but it fails with same problem. I just installed CUDA 6.0 Toolkit followed by instruction of NVIDIA. Is it a

Illegal Memory Access on cudaDeviceSynchronize

|▌冷眼眸甩不掉的悲伤 提交于 2019-11-28 12:59:34
I am encountering a very strange bug in that I get an 'illegal memory access' error when running a Heat 2D simulation of a particular size, but the simulation runs well if I run the exact same simulation, just with fewer elements. Is there a reason that increasing the size of an array would cause this exception? I am using a Titan Black GPU (6 GB of memory), but the simulation I am running is nowhere near that size. I calculated that I could run a 4000 x 4000 simulation, but I get errors if I exceed 250 x 250. The error occurs immediately after I instantiate the array of simulation objects on

States of memory data after cuda exceptions

…衆ロ難τιáo~ 提交于 2019-11-27 22:38:06
CUDA document is not clear on how memory data changes after CUDA applications throws an exception. For example, a kernel launch(dynamic) encountered an exception (e.g. Warp Out-of-range Address), current kernel launch will be stopped. After this point, will data (e.g. __device__ variables) on device still kept or they are removed along with the exceptions? A concrete example would be like this: CPU launches a kernel The kernel updates the value of __device__ variableA to be 5 and then crashes CPU memcpy the value of variableA from device to host, what is the value the CPU gets in this case, 5

Illegal Memory Access on cudaDeviceSynchronize

≡放荡痞女 提交于 2019-11-27 07:26:51
问题 I am encountering a very strange bug in that I get an 'illegal memory access' error when running a Heat 2D simulation of a particular size, but the simulation runs well if I run the exact same simulation, just with fewer elements. Is there a reason that increasing the size of an array would cause this exception? I am using a Titan Black GPU (6 GB of memory), but the simulation I am running is nowhere near that size. I calculated that I could run a 4000 x 4000 simulation, but I get errors if I

States of memory data after cuda exceptions

柔情痞子 提交于 2019-11-26 21:09:51
问题 CUDA document is not clear on how memory data changes after CUDA applications throws an exception. For example, a kernel launch(dynamic) encountered an exception (e.g. Warp Out-of-range Address), current kernel launch will be stopped. After this point, will data (e.g. __device__ variables) on device still kept or they are removed along with the exceptions? A concrete example would be like this: CPU launches a kernel The kernel updates the value of __device__ variableA to be 5 and then crashes