獅子OpenCL上的Xcode 4.2不斷與EXC_BAD_ACCESS暫停

Question

因此，我在Lion上運行Xcode 4.1中的一些簡單的Hello World OpenCL代碼，並且它不斷在clEnqueueTask中斷。當我從MacResearch.org OpenCL tutorials運行源文件時，發生同樣的事情，該文件在clEnqueueNDRangeKernel處中斷。 lldb給出代碼1，地址0x30。

下面是代碼：

#include <stdio.h> 
#include <stdlib.h> 

#include <OpenCL/opencl.h> 

#define MEM_SIZE (128) 
#define MAX_SOURCE_SIZE (0x100000) 

int main() 
{ 

    char *program_source = "\n"\ 
    "__kernel void hello(__global char* string) \n"\ 
    "{           \n"\ 
    " string[0] = 'H';      \n"\ 
    " string[1] = 'e';      \n"\ 
    " string[2] = 'l';      \n"\ 
    " string[3] = 'l';      \n"\ 
    " string[4] = 'o';      \n"\ 
    " string[5] = ',';      \n"\ 
    " string[6] = ' ';      \n"\ 
    " string[7] = 'w';      \n"\ 
    " string[8] = 'o';      \n"\ 
    " string[9] = 'r';      \n"\ 
    " string[10] = 'l';      \n"\ 
    " string[11] = 'd';      \n"\ 
    " string[12] = '!';      \n"\ 
    " string[13] = '\0';      \n"\ 
    "}           \n"\ 
    "\n"; 

    size_t source_size = sizeof(program_source); 

    cl_device_id device_id   = NULL; 
    cl_context context    = NULL; 
    cl_command_queue command_queue = NULL; 
    cl_mem memobj     = NULL; 
    cl_program program    = NULL; 
    cl_kernel kernel    = NULL; 
    cl_platform_id platform_id  = NULL; 
    cl_uint ret_num_devices; 
    cl_uint ret_num_platforms; 
    cl_int ret; 

    char string[MEM_SIZE]; 


    // get platform and device information 
    ret = clGetPlatformIDs(1, &platform_id, &ret_num_platforms); 
    ret = clGetDeviceIDs(platform_id, CL_DEVICE_TYPE_GPU, 1, &device_id, &ret_num_devices); 

    cl_int err = 0; 
    size_t returned_size = 0; 
    size_t buffer_size; 

    // Get some information about the returned device 
    cl_char vendor_name[1024] = {0}; 
    cl_char device_name[1024] = {0}; 
    err = clGetDeviceInfo(device_id, CL_DEVICE_VENDOR, sizeof(vendor_name), vendor_name, &returned_size); 
    err |= clGetDeviceInfo(device_id, CL_DEVICE_NAME, sizeof(device_name),device_name, &returned_size); 
// assert(err == CL_SUCCESS); 
    printf("Connecting to %s %s...\n", vendor_name, device_name); 

    // create OpenCL context 
    context = clCreateContext(NULL, 1, &device_id, NULL, NULL, &ret); 

    // create command queue 
    command_queue = clCreateCommandQueue(context, device_id, 0, &ret); 

    // create memory buffer 
    memobj = clCreateBuffer(context,CL_MEM_READ_WRITE, MEM_SIZE*sizeof(char), NULL, &ret); 

    // create kernel program from source code 
    program = clCreateProgramWithSource(context, 1, (const char **)&program_source, (const size_t*)&source_size, &ret); 

    // build kernel program 
    ret = clBuildProgram(program, 1, &device_id, NULL, NULL, NULL); 

    // create OpenCL Kernel 
    kernel = clCreateKernel(program, "hello", &ret); 

    // set OpenCL kernel parameters 
    ret = clSetKernelArg(kernel, 0, sizeof(cl_mem), (void *)&memobj); 

    // Execute OpenCL kernel 
    ret = clEnqueueTask(command_queue, kernel, 0, NULL, NULL); 

    // copy results from the memory buffer 
    ret = clEnqueueReadBuffer(command_queue, memobj, CL_TRUE, 0, MEM_SIZE*sizeof(char), string, 0, NULL, NULL); 

    // display results 
    puts(string); 

    // finish up 
    ret = clFlush(command_queue); 
    ret = clFinish(command_queue); 
    ret = clReleaseKernel(kernel); 
    ret = clReleaseProgram(program); 
    ret = clReleaseMemObject(memobj); 
    ret = clReleaseCommandQueue(command_queue); 
    ret = clReleaseContext(context); 

    return 0; 
} 

使用malloc的後衛嘗試，得到：

GuardMalloc[OCL_HW-1453]: recording malloc stacks to disk using standard recorder 
GuardMalloc[OCL_HW-1453]: Allocations will be placed on 16 byte boundaries. 
GuardMalloc[OCL_HW-1453]: - Some buffer overruns may not be noticed. 
GuardMalloc[OCL_HW-1453]: - Applications using vector instructions (e.g., SSE) should work. 
GuardMalloc[OCL_HW-1453]: version 24.1 
OCL_HW(1453) malloc: process 1423 no longer exists, stack logs deleted from /tmp/stack-logs.1423.OCL_HW.yL5f5u.index 
OCL_HW(1453) malloc: stack logs being written into /tmp/stack-logs.1453.OCL_HW.pCjTNR.index 
Connecting to NVIDIA GeForce GT 330M... 

我曾與下雪豹和Xcode的3這些代碼沒有問題，我確信不編譯任何.cl文件通過從目標中刪除它們，並且'OpenCl.framework'被鏈接和一切。

我甚至擦乾淨了我的電腦和乾淨的獅子和xcode，但仍然是個問題。我很肯定在這一點上，這是愚蠢的。

- 感謝一堆

Answer 1

你是對的 - 這是愚蠢的。您正在向clCreateProgramWithSource的第四個參數傳遞一個不正確的值。你應該傳遞你的源字符串的長度，但是你傳遞的是指針的大小。你可以這樣修復它：

size_t source_size = strlen(program_source); 

請注意，我通過檢查clBuildProgram的返回值來發現此問題。它是-11，CL_BUILD_PROGRAM_FAILURE，這意味着你的內核編譯失敗。既然你的內核看起來很正常，我這樣做是在命令行：

CL_LOG_ERRORS=stdout ./test 

這引起了蘋果OpenCL實現轉儲編譯器生成日誌到標準輸出。我看到這個：

[CL_BUILD_ERROR] : OpenCL Build Error : Compiler build log: 
<program source>:2:1: error: unknown type name '__kerne' 
__kerne 

<program source>:2:8: error: expected identifier or '(' 
__kerne 

這使我立即想到你的源代碼長度參數有問題。

另外請注意，你需要在你的內核可以改變：

string[13] = '\0'; 

到

string[13] = 0; 

做了這些改變之後，我認爲這對我的MacBook Pro：

Connecting to AMD ATI Radeon HD 6490M... 
Hello, world!