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. Thanks very much for your help.
Regards, Yujie On Fri, Oct 23, 2009 at 9:26 AM, John Peterson < [email protected]> wrote: > On Fri, Oct 23, 2009 at 9:07 AM, Yujie <[email protected]> wrote: > > Dear Roy, > > > > Since I can't understand the whole libmesh until now, I didn't try to > debug > > to find the problem. > > I think the segmentation fault should be from the latest libMesh because > I > > didn't use the variable "remote_elem" directly. Thanks for your help. > > What Roy has been trying to explain, is that it doesn't matter that > you don't use remote_elem directly. Illegal memory accesses and > segmentation faults are funny like that: they crop up in places where > you don't expect them. > > -- > John > ------------------------------------------------------------------------------ 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
