Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: [OMPI devel] Debug output issues on the trunk
From: Ralph Castain (rhc_at_[hidden])
Date: 2013-04-29 22:33:30

Hi folks

I've been encountering problems where setting "verbosity" values doesn't result in any output. I finally tracked it down the not-too-recent overhaul of the MCA parameter system. At that time, the mca_component_open function was replaced with a framework_open function, and the "verbose_output" parameter was removed in favor of a default framework_output variable that exists in the framework object itself.

Unfortunately, when the change was made, the original verbose output variables (in many places) were not removed. Thus, everything compiles - but the verbosity parameter for that framework has no effect. I've now found/fixed four frameworks where this occurred - after wasting a ton of time and frustration :-(

So if you are trying to get debug output in a debug build, and setting a verbosity yields no output, check the opal_output_verbose and OPAL_OUTPUT_VERBOSE calls to ensure they are looking at the framework_output channel and not the old one. Quite likely, it wasn't updated.

Meantime, I'm hoping to enlist help in slowly trolling thru all the frameworks and components to correct the situation. Volunteers are appreciated as this is going to take some time to fix.