> > Whenever I see a segfault coming from a weird place, in this case, > from the destructor of std::string, I usually suspect an incomplete > recompile of some sort. For example, object files from an older > compiler version getting linked with object files from a new one, etc. > Can you see if 'make clobber' and remaking in dbg mode doesn't fix > the problem?
Hi John, Thanks a lot for your answer. I have tried "make clobber" and also "make distclean" but unfortunately, nothing has changed. But, when compiling, e.g., the examples, I also get the following two warnings (also in opt mode): ld: warning: duplicate dylib /opt/local/lib/libz.1.dylib ld: warning: duplicate dylib /usr/local/lib/libgcc_s.1.dylib I have seen them from the very beginning but used to ignore them since in opt mode everything seems to be good. That is why I forgot to mention them earlier. -Anna ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
