![]() Wall -Wno-parentheses -Wno-non-virtual-dtor -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-st TBBmalloc: BUILD_COMMAND g++ -DDO_ITT_NOTIFY -g -O2 -DUSE_PTHREAD -m64 -mrtm -fPIC -D_TBB_BUILD=1 TBBmalloc: BUILD_KERNEL Linux 4.5.1-1-ARCH #1 SMP PREEMPT Thu Apr 14 19:19:32 CEST 2016 ![]() Is there anything else that I might be missing? I did not have any task scheduler init before, so I added the object in the beginning of my main() so that it is there, and stays. Now I do have TBB calls in other threads that work, and it seems that this is related to from which thread parallel_for() is called. =16218= by 0x583FBE: rgb::RGBDisplay::execute(std::map, std::allocator >, boost::any, std::less, std::allocator >, std::allocator, std::allocator > const, boost::any>&, ProgressObserver*) (in /home/ypnos/work/gerbil/master/build-release/bin/qgerbil) =16218= by 0圆8A9724: tbb::internal::allocate_root_with_context_proxy::allocate(unsigned long) const (in /usr/lib/libtbb.so.2) ![]() ![]() I found that it doesn't really matter what my parallel task is doing and even the following code leads to a segmentation fault: tbb ::parallel_for ( tbb :: blocked_range2d (0, 255, // row range 0, 255 ), // column range ( const tbb :: blocked_range2d &r ), po=0x33d1020) at. This is code that worked before, and for quite a while so. Today I found that my application crashes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |