On Thu, Apr 18, 2013 at 11:11 AM, Roy Stogner wrote:
>
> 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;
>
Nothing funnier than hearing Derek say that the scaling is terrible
If you are using PETSc underneath, one option is
http://www.mcs.anl.gov/petsc/petsc-current/docs/manualpages/Sys/PetscSynchronizedPrintf.html
It uses C-style formatted output, but will take care of the message
ordering.
Dmitry.
On Thu, Apr 18, 2013 at 12:11 PM, Roy Stogner wrote:
>
> On Thu, 18
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 al
And don't forget my favorite debugging tool:
sleep(libMesh::processor_id())
std::cerr << "Stuff!" << std::endl;
Yep, it's old school - but it really helps to order output when you're
trying to track down some problem... JUST DONT FORGET TO TAKE THOSE SLEEP
STATEMENTS OUT BEFORE COMMITTING YOUR CO
On Thu, Apr 18, 2013 at 8:00 AM, Kirk, Benjamin (JSC-EG311) <
benjamin.kir...@nasa.gov> wrote:
> On Apr 18, 2013, at 8:33 AM, Manav Bhatia wrote:
>
> > I am curious if there are any recommended practices and/or open source
> debugging tools for MPI codes. What are the tools used by the libMesh
>
On Apr 18, 2013, at 8:33 AM, Manav Bhatia wrote:
> I am curious if there are any recommended practices and/or open source
> debugging tools for MPI codes. What are the tools used by the libMesh
> developers?
Open source? sadly, the best I've come up with is
$ mpirun -np # … -start_in_debug
Hi,
I am curious if there are any recommended practices and/or open source
debugging tools for MPI codes. What are the tools used by the libMesh
developers?
Thanks,
Manav
--
Precog is a next-generation analytics
