After configuring with --with-tbb=/usr --with-tbb-lib="-ltbb -ltbbmalloc" (can't the first option be autodetected and the latter option be assumed, by the way?) and recompiling, I get the following when running the example programs with "mpirun -np 4":
rm_l_2_26531: p4_error: interrupt SIGSEGV: 11 rm_l_2_26531: (0.651229) net_send: could not write to fd=5, errno = 32 rm_l_3_26602: p4_error: interrupt SIGSEGV: 11 rm_l_3_26602: (0.381278) net_send: could not write to fd=5, errno = 32 rm_l_1_26460: p4_error: interrupt SIGSEGV: 11 rm_l_1_26460: (0.976042) net_send: could not write to fd=5, errno = 32 The segfaults are always after the program's completed, so it's not an extremely urgent problem, but it's probably still something to look into. Is there something more than just deleting the Threads task_scheduler that needs to be done in libMesh::close()? --- Roy ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
