Hi John, Please see my reply below.
On 05/01/2014 05:44 PM, John Peterson wrote: > > > > On Thu, May 1, 2014 at 3:39 PM, Dafang Wang <[email protected] > <mailto:[email protected]>> wrote: > > Hi John, > > Please ignore my last post that speculated the bug was on GetPot. > There is an error in my test code. > > So back to my original question and your reply in the first round, > let me clarify a few things: > > 1. I simply passed argv to LibMeshInit(). I did no preprocessing > of argv. > > 2. As you pointed out, the bug occurred at libmesh.C, line 356, > which is "libmesh_assert(remote_elem);". This line then caused a > problem with ostream. Although this line is unlikely to cause a > seg fault as you said, the error did occur here. > > 3. This error occurred only on one cluster. I did not encounter > this seg-fault error on another two machines. All three machines > were running libmesh 0.9.2 with the RelWithDebInfo mode. Such > inconsistent performance across platforms is confusing. > > > RelWithDebInfo mode? Sorry, I was building the libmesh in the optimized mode (as opposed to the debug mode). RelWithDebInfo is the mode of my user program. > > > Here is the latest error message (passing argvs to LibmeshInit(), > without "--keep-cout" ): > ==3239== Process terminating with default action of signal 11 > (SIGSEGV) > ==3239== Access not within mapped region at address 0x0 > ==3239== at 0x3542F853F8: > std::ostream::sentry::sentry(std::ostream&) (in > /usr/lib64/libstdc++.so.6.0.3) > ==3239== by 0x3542F8557D: std::basic_ostream<char, > std::char_traits<char> >& std::operator<< <std::char_traits<char> > >(std::basic_ostream<char, std::char_traits<char> >&, char const*) > (in /usr/lib64/libstdc++.so.6.0.3) > ==3239== by 0x6D18491: libMesh::BasicOStreamProxy<char, > std::char_traits<char> >& libMesh::BasicOStreamProxy<char, > std::char_traits<char> >::operator<< <char[32]>(char[32] const&) > (ostream_proxy.h:124) > ==3239== by 0x6D76ECB: > _ZN7libMesh11LibMeshInitC9EiPKPKcP19ompi_communicator_t > (libmesh.C:356) > ==3239== by 0x6D793BD: libMesh::LibMeshInit::LibMeshInit(int, > char const* const*, ompi_communicator_t*) (libmesh.C:0) > ==3239== by 0x4387B3: main (main_RealHeart.cpp:303) > > > > Whenever I see an error down in the standard library like this, I > usually suspect an invalid/bad build of libmesh. Do you get the > segfault in both debug and optimized modes? Have you tried making > clean and recompiling the library? No, I have not yet tried the debug mode. As for recompiling the library, did you mean Libmesh, petsc, or my own program? I did try "make clean" and rebuilding my user program. Thanks, Dafang > > -- > John -- Dafang Wang, Ph.D Postdoctoral Fellow Institute of Computational Medicine Department of Biomedical Engineering Johns Hopkins University Hackerman Hall Room 218 Baltimore, MD, 21218 ------------------------------------------------------------------------------ "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 [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
