On Thu, 18 Apr 2013, Derek Gaston wrote: > And don't forget my favorite debugging tool: > > sleep(libMesh::processor_id()) > std::cerr << "Stuff!" << std::endl;
I do this exact same horrible horrible thing too, but in these conditions it should often be better to use "--redirect-stdout" as an alternative, which spits each processor's messages to its own file. Time stamp everything or stick in a few barrier() calls so you can infer message ordering, and that way you don't end up waiting forever when you're trying to debug something deep in a loop. --- Roy ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
