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.margo...@mail.huji.ac.il> wrote: > Hi, > > 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. > > Thanks, > Alex > > 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 > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
