On Thu, 19 Nov 2009, Vijay S. Mahadevan wrote: > I just updated, clobbered and ran make on my head svn version of > libmesh. Just to test if the library is working correctly, ran ex4 in > both 1 and 2 processors. In serial, the code ran as intended but on > two processors, I get segfaults.
I can reproduce this; I'm running it through the debugger now... --- Roy > Following is the assertion failure in debug mode that causes the crash: > > mpiexec -n 2 ./ex4-opt -d 2 -n 5 > > Assertion `cnt < global_indices.size()' failed. > [0] src/partitioning/partitioner.C, line 190, compiled Nov 19 2009 at 15:31:11 > terminate called after throwing an instance of 'libMesh::LogicError' > what(): Error in libMesh internal logic > [compute-00:04739] *** Process received signal *** > [compute-00:04739] Signal: Aborted (6) > [compute-00:04739] Signal code: (-6) > [compute-00:04739] [ 0] /lib64/libpthread.so.0 [0x3577a0de60] > [compute-00:04739] [ 1] /lib64/libc.so.6(gsignal+0x35) [0x3576e30045] > [compute-00:04739] [ 2] /lib64/libc.so.6(abort+0x110) [0x3576e31ae0] > [compute-00:04739] [ 3] > /usr/local/gcc/4.3.2/lib64/libstdc++.so.6(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x114) > [0x2aaab2e7ce94] > [compute-00:04739] [ 4] /usr/local/gcc/4.3.2/lib64/libstdc++.so.6 > [0x2aaab2e7b296] > [compute-00:04739] [ 5] /usr/local/gcc/4.3.2/lib64/libstdc++.so.6 > [0x2aaab2e7b2c3] > [compute-00:04739] [ 6] /usr/local/gcc/4.3.2/lib64/libstdc++.so.6 > [0x2aaab2e7b3aa] > [compute-00:04739] [ 7] > /emchome/vijaysm/soft/libmesh-dev-3.0/lib/x86_64-unknown-linux-gnu_dbg/libmesh.so(_ZN11Partitioner32partition_unpartitioned_elementsER8MeshBasej+0x9d9) > [0x2aaaabad8f7b] > [compute-00:04739] [ 8] > /emchome/vijaysm/soft/libmesh-dev-3.0/lib/x86_64-unknown-linux-gnu_dbg/libmesh.so(_ZN11Partitioner9partitionER8MeshBasej+0x8d) > [0x2aaaabad9d6d] > [compute-00:04739] [ 9] > /emchome/vijaysm/soft/libmesh-dev-3.0/lib/x86_64-unknown-linux-gnu_dbg/libmesh.so(_ZN8MeshBase9partitionEj+0x60) > [0x2aaaab7cdd2e] > [compute-00:04739] [10] > /emchome/vijaysm/soft/libmesh-dev-3.0/lib/x86_64-unknown-linux-gnu_dbg/libmesh.so(_ZN8MeshBase15prepare_for_useEb+0x61) > [0x2aaaab7cdd91] > [compute-00:04739] [11] > /emchome/vijaysm/soft/libmesh-dev-3.0/lib/x86_64-unknown-linux-gnu_dbg/libmesh.so(_ZN9MeshTools10Generation10build_cubeER16UnstructuredMeshjjjddddddN12libMeshEnums8ElemTypeEb+0xf04a) > [0x2aaaab860227] > [compute-00:04739] [12] ./ex4-dbg(main+0xd26) [0x448556] > [compute-00:04739] [13] /lib64/libc.so.6(__libc_start_main+0xf4) > [0x3576e1d8a4] > [compute-00:04739] [14] > ./ex4-dbg(_ZN10SerialMesh21ancestor_elements_endEv+0x69) [0x444d69] > > Did I miss something when updating the new code ? My config command was: > > ./configure --enable-everything=yes --enable-shared=yes > --with-mpi=/usr/local/openmpi --enable-petsc --disable-vtk > --enable-slepc --enable-complex=no --disable-ghosted > --enable-exceptions > > I wonder if disabling libHilbert is causing this ? Any help on this > would be great because this is the simplest test case I have. > > Vijay > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Libmesh-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/libmesh-devel > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
