Question

我在C ++下使用opnemp库在我的mac上测试一个简单的helloword，通过终端使用以下两个命令：

/usr/local/bin/clang++-omp -fopenmp helloworld.cpp -o test
/usr/local/bin/valgrind  --tool=helgrind --log-file=a.log ./test

输出正确：

warning: no debug symbols in executable (-arch x86_64)
Hello World from thread = 0
Hello World from thread = 1
Hello World from thread = 3
Hello World from thread = 2
Number of threads = 4

但是日志文件（a.log）包含：“来自231个上下文的174986个错误”（作为错误摘要）

这是日志文件的一部分：

==643== ---Thread-Announcement------------------------------------------
==643== 
==643== Thread #1 is the program's root thread
==643== 
==643== ----------------------------------------------------------------
==643== 
==643== Possible data race during read of size 4 at 0x10057C118 by thread #3
==643== Locks held: none
==643==    at 0x10055D1F4: spin_lock (in /usr/lib/system/libsystem_platform.dylib)
==643==    by 0x10057092D: _pthread_start (in /usr/lib/system/libsystem_pthread.dylib)
==643==    by 0x10056E384: thread_start (in /usr/lib/system/libsystem_pthread.dylib)
==643== 
==643== This conflicts with a previous write of size 4 by thread #1
==643== Locks held: none
==643==    at 0x10055D200: spin_unlock (in /usr/lib/system/libsystem_platform.dylib)
==643==    by 0x1000434B0: __kmp_create_worker (in /usr/local/Cellar/libiomp/20150701/lib/libiomp5.dylib)
==643==    by 0x100031E3D: __kmp_allocate_thread (in /usr/local/Cellar/libiomp/20150701/lib/libiomp5.dylib)
==643==    by 0x10002E7A1: __kmp_allocate_team (in /usr/local/Cellar/libiomp/20150701/lib/libiomp5.dylib)
==643==    by 0x10002FA2D: __kmp_fork_call (in /usr/local/Cellar/libiomp/20150701/lib/libiomp5.dylib)
==643==    by 0x100027F0D: __kmpc_fork_call (in /usr/local/Cellar/libiomp/20150701/lib/libiomp5.dylib)
==643==    by 0x100000CE8: main (in ./test)
==643==  Address 0x10057c118 is in the Data segment of /usr/lib/system/libsystem_pthread.dylib

“helloworld”的代码是：

#include <stdio.h>
#include <libiomp/omp.h>
#include <stdlib.h>
int main (int argc, char *argv[]) {   
int nthreads=4, tid;
#pragma omp parallel num_threads(nthreads) private(tid)
 {

    //Obtain thread number
    tid = omp_get_thread_num();
    printf("Hello World from thread = %d\n", tid);

    // Only master thread does this
    if (tid == 0)
    {
        printf("Number of threads = %d\n", nthreads);
    }

 } 
return 0;
}

有没有人知道这些错误（数据竞争）？我没有这些线程之间的共享数据。

Answer 1

这很可能是假阳性。有关libgomp的相同问题，请参阅例如similar discussion。它也可能是libiomp / pthread实现中的实际问题，但这似乎不太可能。

你似乎无能为力。通常，如果堆栈的顶部位于库中，则它是库中的误报或错误，或者您正在滥用它（例如，在多个线程的缓冲区上运行memcpy）。

如果你的二进制文件位于堆栈顶部，那么你的代码就更明显了。

你的代码很好。数据竞赛。

Mac OS X上的C ++ openmp El Capitan，Valgrind错误（数据竞争）

1 个答案: