On Thu, 9 Apr 2009, Tim Kroeger wrote: > BTW: Why is --enable-tracefiles not enabled by default? It shouldn't bother > anybody since it doesn't do anything as long as the application doesn't > crash, does it? And if it *does* crash, this option is very useful.
Hmm... I think I was worried about compatibility. Check out the nastiness in print_trace.C; the current implementation requires gcc and glibc-compatible non-standard features. I guess we've now got those safely wrapped in specific autoconf tests for name demangling and backtracing, though. Any other votes for/against enabling tracefiles by default? --- Roy ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
