Configuring the Tracing
-----------------------
-The :ref:`tracing subsystem <outcomes_vizu>` can be configured in
+The :ref:`tracing subsystem <outcome_vizu>` can be configured in
several different ways depending on the used interface (S4U, SMPI, SimDag)
and the kind of traces that needs to be obtained. See the
:ref:`Tracing Configuration Options subsection
.. TODO:: All available collective algorithms will be made available
via the ``smpirun --help-coll`` command.
+.. _cfg=smpi/finalization-barrier:
+
Add a barrier in MPI_Finalize
.............................
-.. _cfg=smpi/finalization-barrier:
-
**Option** ``smpi/finalization-barrier`` **default:** off
By default, SMPI processes are destroyed as soon as soon as their code ends,
.. _cfg=smpi/errors-are-fatal:
+Render MPI errors non-fatal
+...........................
+
**Option** ``smpi/errors-are-fatal`` **default:** on
By default, SMPI processes will crash if a MPI error code is returned. MPI allows
.. _cfg=smpi/pedantic:
+Disable pedantic MPI errors
+...........................
+
**Option** ``smpi/pedantic`` **default:** on
By default, SMPI will report all errors it finds in MPI codes. Some of these errors
may not be considered as errors by all developers. This flag can be turned off to
avoid reporting some usually harmless mistakes.
Concerned errors list (will be expanded in the future):
- - Calling MPI_Win_fence only once in a program, hence just opening an epoch without
- ever closing it.
+
+ - Calling MPI_Win_fence only once in a program, hence just opening an epoch without
+ ever closing it.
.. _cfg=smpi/iprobe:
- ``-gdb`` is equivalent to ``-wrapper "gdb --args" -keep-temps``, to run within gdb debugger
- ``-lldb`` is equivalent to ``-wrapper "lldb --" -keep-temps``, to run within lldb debugger
-- ``-vgdb`` is equivalent to ``-wrapper "valgrind --vgdb=yes --vgdb-error=0"
--keep-temps``, to run within valgrind and allow to attach a debugger
+- ``-vgdb`` is equivalent to ``-wrapper "valgrind --vgdb=yes --vgdb-error=0" -keep-temps``,
+ to run within valgrind and allow to attach a debugger
To help locate bottlenecks and largest allocations in the simulated application,
the -analyze flag can be passed to smpirun. It will activate