dd9a819a1c
It is verbotten to use opal_output() after the fork() but before the exec()! It results in all manner of undefined behavior. For example, on some OS X systems, if you run a trivial "hello world" MPI program with a high level of ODLS verbosity: ```sh $ mpirun -np 3 --mca odls_base_verbose 100 ./hello_c ``` You will see a bunch of output from the mpirun ODLS base, but then it *may* hang in odls_default_module.c:do_child() -- after the fork() but before the exec() -- while trying to opal_output() some debugging statements. The solution is to remove these extraneous opal_output() statements. Indeed, the ODLS base is already outputting the same information that these opal_output() statements are trying to emit, anyway. Signed-off-by: Jeff Squyres <jsquyres@cisco.com> |
||
|---|---|---|
| .. | ||
| bindings | ||
| etc | ||
| include | ||
| mca | ||
| orted | ||
| runtime | ||
| test | ||
| tools | ||
| util | ||
| common_sym_whitelist.txt | ||
| Doxyfile | ||
| Makefile.am | ||