On Wed, Apr 30, 2014 at 3:08 PM, Dafang Wang <dafang.w...@jhu.edu> wrote:
> Hi, > > I got a segfault error when running my libmesh program on a single > thread (but on a cluster). What is odd is that the same code ran well on > two other computers (one is cluster and the other a desktop). The > segfault error has to do with LibmeshInit() and ostream, which is also > odd to me. > > The version of libmesh I am using is 0.9.2.2. > > Any suggestions will be greatly appreciated. The error is described below. > ==13923== by 0x6D76ECB: > _ZN7libMesh11LibMeshInitC9EiPKPKcP19ompi_communicator_t (libmesh.C:356) In the 0.9.2.2 tagged version, line 356 of libmesh.C is libmesh_assert(remote_elem); I don't think that line could cause a segfault... are you running in debug mode? ==13923== by 0x439AF8: main (main_RealHeart.cpp:292) > ==13923== Address 0x0 is not stack'd, malloc'd or (recently) free'd What's on line 292 of your main_RealHeart.cpp file? -- John ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
