Looking at your cmd line, it looks like you are trying to get diagnostic output from the mapper? If so, that cmd line is totally wrong. First, there are no "OPAL_OUTPUT" calls (at least, that I know of) in the orte layer as I studiously avoid them. Instead, everything is either cap or lower case opal_output_verbose. The cap version is only in the debug builds.
Regardless, you are almost certainly not seeing any output because you aren't passing the right param. You need something like this:
oshrun -map-by node -np 2 -mca rmaps_base_verbose 10 ./examples/ring_oshmem
That will output the diagnostics from the mapper framework.
On Feb 17, 2014, at 3:40 AM, Jeff Squyres (jsquyres) <jsquyres_at_[hidden]> wrote:
> OPAL_OUTPUT is the exact equivalent of opal_output(), except that it is complied out for non-debug builds.
> So if you did a production build (E.g., a vpath build), OPAL_OUTPUT() will be compiled out. Otherwise, we typically use stream 0 for debugging stuff.
> On Feb 17, 2014, at 3:21 AM, Alex Margolin <alex.margolin_at_[hidden]> wrote:
>> I'm having trouble getting the OPAL_OUTPUT to print. I'm trying the following command line (with no success):
>> `pwd`/osh_install/bin/oshrun --map-by node -np 2 -mca orte_debug true -mca orte_debug_verbose 100 -mca orte_report_silent_errors true -mca orte_map_stddiag_to_stderr true ./examples/ring_oshmem
>> How can I get it to print these strings? Online search was surprisingly fruitless.
>> P.S. all the mca params are available if I look at "oshmem_info -a", so I suppose I can use them, but there are a lot more params so I'm not sure what I need to add here...
>> devel mailing list
> Jeff Squyres
> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
> devel mailing list