On Tue, Jul 8, 2014 at 6:32 PM, Derek Gaston <fried...@gmail.com> wrote: > Have you tried disabling TBB? That might show something interesting.
So, I can confirm that configuring libmesh with --disable-tbb --disable-cxx11 gets rid of the valgrind error. Since all the valgrind errors seem to have this "scalable_free" function ==11839== by 0x8915A14: scalable_free (frontend.cpp:2564) at their root, I'm currently blaming the combination of .) tbb::scalable_allocator .) GCC4.6 .) no -std=c++0x for this issue. The next thing I'll try is re-enabling tbb, but removing the scalable_allocator template parameters from dof_map.h and sparsity_pattern.h, and making sure we're still valgrind-clean. Assuming this works, what is the correct long-term fix? scalable_allocator seems to be an optimization, so the simplest approach is to just remove it... I wouldn't be opposed to e.g. enabling it only when C++11 is enabled, although that is quite a hack, and only shows that we do not know what the real problem is. -- John ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
