From: Roy S. <roy...@ic...> - 2010-03-29 20:17:16
|
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 |
From: John P. <pet...@cf...> - 2010-03-29 20:56:47
|
On Mon, Mar 29, 2010 at 3:17 PM, Roy Stogner <roy...@ic...> wrote: > > 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. Any chance you are using an older version of valgrind? This bugzilla http://bugs.kde.org/show_bug.cgi?id=147498 claims "3.3.0 works with TBB out of the box." and that was back in Jan 2008... -- John |
From: Roy S. <roy...@ic...> - 2010-03-29 21:10:19
|
On Mon, 29 Mar 2010, John Peterson wrote: > Any chance you are using an older version of valgrind? This bugzilla > > http://bugs.kde.org/show_bug.cgi?id=147498 > > claims > > "3.3.0 works with TBB out of the box." > > and that was back in Jan 2008... Hmm... we're on Ubuntu 8.04 for at least another month or two here, and that's pretty old, but "valgrind --version" says "valgrind-3.3.0-Debian". But perhaps this is a different bug that's fixed in a less ancient valgrind. I'll give that test case a shot on my home computer and see what happens. Thanks, --- Roy |
From: Roy S. <roy...@ic...> - 2010-03-29 23:04:34
|
On Mon, 29 Mar 2010, Roy Stogner wrote: > But perhaps this is a different bug that's fixed in a less ancient > valgrind. I'll give that test case a shot on my home computer and see > what happens. Update: with valgrind 3.5.0, that test case worked fine. --- Roy |