On Mon, 2 Jun 2008, Derek Gaston wrote: > How do I provide a full stack trace again?
--enable-tracefiles or --enable-everything will try to have stack traces print to output files in the current directory automatically whenever an assert fails. But that only works with gcc/glibc at the moment, I think; since you can replicate the bug in serial, you're probably better off just running the code in gdb and running "where" after it breaks. > BTW: I did some testing... and even converting the mesh to xda then > running the simulation using the xda mesh causes it to hit the same > problem... so it's not just Exodus. > > ParallelMesh still isn't on by default in SVN right? Definitely not; I haven't had time to work on it lately, and it's still got a couple bugs triggered by adaptive coarsening, plus whatever bugs I don't know about yet because my test codes never make it past the first bugs. ;-) --- Roy ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
