On Fri, 23 Oct 2009, Yujie wrote:
> I find the problem. Since my codes was run in old libMesh, I just > replace libMesh::init() with LibmeshInit init(). I didn't remove > libMesh::close(), leading to the segmentation fault. Ah! I'm a fool. It occurred to me that this might be the problem, but somehow the part of my brain responsible for remembering "in C++ it's okay to call delete on a NULL pointer" decided to mistakenly add "in C++ it's okay to call delete on an already-deleted pointer". That second delete is what killed your program. > Thanks very much for your help. You're welcome. Thanks for reporting the error; even if the flaw was technically in user-level code, that sounds like too easy a mistake to make. I'll throw an assertion in libMesh::_close() to make sure it's never called after we've already closed out. --- Roy ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
