Note that there are some explanatory texts on larger screens.

plurals
  1. POcuda: allocating array of pointers to images and the images
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. COSo this is a debugging question? Perhaps you could change the title to reflect this? Are you sure you haven't just edited the source file for the program without recompiling it?
      singulars
    2. COHow about some [error checking](http://stackoverflow.com/questions/14038589/what-is-the-canonical-way-to-check-for-errors-using-the-cuda-runtime-api) on your cuda calls? For an arrangement of pointers to pointers to be accessible on the device, you cannot cudaMalloc the top level pointer and then cudaMalloc pointers beneath it. It's necessary to create a pointer arrangement on the host and then copy it to the device. See [this question/answer](http://stackoverflow.com/questions/14790999/how-to-pass-a-c-class-with-array-of-pointers-to-cuda/14791979#14791979) for an example.
      singulars
    3. COAlso, this line: `if(_devStackImagesCuda[i] == NULL)` is dereferencing a device pointer in host code. This is illegal and won't work (segfault). So this method of trying to determine whether or not a device pointer needs to be cudaMalloc'ed by testing if the device pointer is zero (on the host) is a bad idea. If you really wanted to, you could cudaMemcpy the pointer back to the host before testing if it is zero, but I would look for a better way to get my allocations done.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload