Home/ Questions/Q 6194519
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-24T03:18:36+00:00

I’m debugging my CUDA 4.0/Thrust-based image reconstruction code on my Ubuntu 10.10 64-bit system

  • 0

I’m debugging my CUDA 4.0/Thrust-based image reconstruction code on my Ubuntu 10.10 64-bit system and I’ve been trying to figure out how to debug this run-time error I have in which my output images appear to some random “noise.” There is no random number generator output in my code, so I expect the output to be consistent between runs, even if it’s wrong. However, it’s not…

I was just wondering if any one has a general procedure for debugging CUDA runtime errors such as these. I’m not using any shared memory in my cuda kernels. I’ve taken pains to avoid any race conditions involving global memory, but I could have missed something.

I’ve tried using gpu ocelot, but it has problems recognizing some of my CUDA and CUSPARSE function calls.

Also, my code generally works. It’s just when I change this one setting that I get these non-deterministic results. I’ve checked all code associated with that setting, but I can’t figure out what I’m doing wrong. If I can distill it to something that I can post here, I might do that, but at this point it’s too complicated to post here.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Are you sure all of your kernels have proper blocksize/remainder handling? The one place we have seen non-deterministic results occurred when we had data elements at the end of the array not being processed.

    Our kernels were originally were intended for data that was known to be an integer multiple of 256 elements. So we used a blocksize of 256, and did a simple division to get the number of blocks. When the data was then changed to be any length, the leftover 255 or less elements never got processed. Those spots in the output then had random data.

    • 0