> In that case, would you try using a custom compilation method? Try > building (after a clean) in devel mode, but with a CXXFLAGS > environment variable set to include "-D_GLIBCXX_DEBUG > -D_GLIBCXX_DEBUG_PEDANTIC" > > If that breaks, then it's probably some problem specific to your OS X > GCC build. Wouldn't be the first time they'd messed up that feature: > > http://stackoverflow.com/questions/1416096/c-debug-builds-broke-in-snow-leopard-x-code > --- > Roy
Yes, that breaks, too: Program received signal SIGABRT, Aborted. 0x00007fff853623d6 in __kill () (gdb) bt #0 0x00007fff853623d6 in __kill () #1 0x00007fff85402972 in abort () #2 0x00007fff8531a615 in free () #3 0x0000000102a75b8a in std::basic_stringbuf<char, std::char_traits<char>, std::allocator<char> >::overflow () #4 0x0000000102a7a0cc in std::basic_streambuf<char, std::char_traits<char> >::xsputn () #5 0x0000000102a706e5 in std::__ostream_insert<char, std::char_traits<char> > () #6 0x0000000102a70961 in std::operator<< <std::char_traits<char> > () #7 0x00000001011fcd39 in libMesh::MeshBase::get_info (this=<value temporarily unavailable, due to optimizations>) at src/mesh/mesh_base.C:228 #8 0x00000001011fd162 in libMesh::MeshBase::print_info (this=0x101881a4f, o...@0x102aea5c0) at src/mesh/mesh_base.C:248 #9 0x0000000100003c7f in main (argc=6, argv=0x7fff5fbff7b0) at ex4.C:216 What exactly does this tell me now? -Anna ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
