we have problems only when adding new code and need to debug it.
will revert back you change.


On Tue, Apr 8, 2014 at 1:58 AM, Jeff Squyres (jsquyres)
<jsquy...@cisco.com>wrote:

> On Apr 7, 2014, at 6:39 PM, Mike Dubman <mi...@dev.mellanox.co.il> wrote:
>
> > somehow we run it with both, --verbose not enough to understand the
> problem and --debug is too much.
> >
> > maybe --trace is here to rescue?
>
> It won't really solve the problem; it'll just create another level of
> argument about where a given message should go (now there will be 3 levels
> instead of 2... eventually there will be 4, and then 5, and then ...).
>
> Do you really need to run with --debug all the time?  I.e., do you have so
> many problems with MTT itself that you need to run with --debug?
>
> --
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/
>
> _______________________________________________
> mtt-devel mailing list
> mtt-de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel
>

Reply via email to