[Trilinos-Users] tracking down NaNs: best practices?

[Nico Schlömer]

Hi all,

I'm just trying to track down some NaNs that (sometimes) appear on mpi 
runs in a code that touches various Trilinos packages.
Doing so, I find myself climbing through Trilinos methods and the 
classes with plenty of 'std::cout's which obviously takes much time. 
There must be a better way to do this. (Trilinos compile options, helper 
methods...?)

Any hints?

Cheers,
Nico