Does anyone have valgrind working well with Threaded Building Blocks
enabled? My first attempt to try that distills down to this failure:
Program:
#include "tbb/task_scheduler_init.h"
int main (int argc, char** argv)
{ tbb::task_scheduler_init test_scheduler(1); return 0; }
Compilation:
g++ -I$TBB_INC -o test.exe test.C -L$TBB_LIB_PATH -ltbb
Execution:
valgrind ./test.exe
==10339== Invalid read of size 8
...
==10339== by 0x4E363E2: tbb::internal::dynamic_link(char const*,
tbb::internal::dynamic_link_descriptor const*, unsigned long, unsigned long,
void**) (in
/org/centers/pecos/LIBRARIES/TBB/tbb-2.2.013-intel-10.1/linux_intel64_icc_cc4.2.4_libc2.7_kernel2.6.24_release/libtbb.so.2)
...
and one similar error in the same function.
I'd like to start asserting that our libMesh BuildBot tests all make
valgrind happy, but that can't happen if merely initializing one of
our dependency libraries makes it unhappy.
---
Roy
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users
