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.
Regards, Yujie On Fri, Oct 23, 2009 at 8:52 AM, Roy Stogner <[email protected]>wrote: > > > On Fri, 23 Oct 2009, Yujie wrote: > > Thanks Roy. Actually, I use LibMeshInit to result in this error. I replace >> it with libmesh::init(). The error disappears. >> > > The error message disappears, but the error is just hidden. Before, > there was some corruption in your program that was revealed when doing > memory cleanup. Skipping the cleanup does not fix the underlying > problem. > > However, what does "*** Warning, This code is deprecated, and likely >> to be removed in future library versions! src/base/libmesh.C, line >> 356, compiled Oct 22 2009 at 16:18:19 *** " mean? >> > > It means that you're using obsolete code; we replaced ::init() and > ::close() with the libMeshInit constructor and destructor. The > original functions are still there for backwards compatibility now, > but will be removed eventually. > --- > 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
