Thanks Roy. Actually, I use LibMeshInit to result in this error. I replace it with libmesh::init(). The error disappears. 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? When I run the codes, it is shown. Thanks again.
Regards, Yujie On Thu, Oct 22, 2009 at 5:42 PM, Roy Stogner <[email protected]>wrote: > > On Thu, 22 Oct 2009, Yujie wrote: > > I use the latest version to run my codes. However, there is a segmentation >> fault. I debug the codes. I find the error is generated in >> src/base/libmesh.c:245 when the codes running is almost finished. Could >> you >> give me some help? thanks a lot. >> > > remote_elem gets deleted there, which would cause a problem if it > hadn't already been allocated on line 153. I don't suppose you could > be calling libMesh::close() without first calling libMesh::init()? We > now use a LibMeshInit object constructor/destructor to try to make > such errors impossible. > > Otherwise, you've probably got an error somewhere else in your code > which is overwriting the value of the remote_elem pointer or the > memory management information around what it points to. Either way > that would be hell to debug. I'd try METHOD=dbg and valgrind, if you > haven't already. > --- > 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
