It seems ex29 is ok if I configure petsc without "--with-fc=g95" option.
On Mon, Nov 14, 2011 at 12:45 PM, Roy Stogner <[email protected]>wrote: > > On Mon, 14 Nov 2011, Kyunghoon Lee wrote: > > I did svn up, which updated ex30, but I still got the same error. I did >> run in a debug mode, but I'm not sure why I got no stack. >> > > The libMesh terminate handler catches C++ exceptions; gdb intercepts > segfaults... but on PETSc errors, we've got nothing in place to catch > the problem before program exit. My workaround has always been to > re-run and step through the program manually, but in hindsight I > suppose we ought to be figuring out something appropriate to give to > PetscPushErrorHandler()? > --- > Roy > ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
