Display leak origin in message, if -trace-call-location is used.

[simgrid.git] / teshsuite / smpi / coll-allreduce-with-leaks / mc-coll-allreduce-with-leaks.tesh

diff --git a/teshsuite/smpi/coll-allreduce-with-leaks/mc-coll-allreduce-with-leaks.tesh b/teshsuite/smpi/coll-allreduce-with-leaks/mc-coll-allreduce-with-leaks.tesh
index 3a93258..51f0f52 100644 (file)
--- a/teshsuite/smpi/coll-allreduce-with-leaks/mc-coll-allreduce-with-leaks.tesh
+++ b/teshsuite/smpi/coll-allreduce-with-leaks/mc-coll-allreduce-with-leaks.tesh
@@ -9,14 +9,15 @@ $ $VALGRIND_NO_LEAK_CHECK ${bindir:=.}/../../../smpi_script/bin/smpirun -wrapper
 > [0.000000] [mc_safety/INFO] Check a safety property. Reduction is: dpor.
 > [0.000000] [smpi_utils/INFO] Probable memory leaks in your code: SMPI detected 8 unfreed MPI handles : display types and addresses (n max) with --cfg=smpi/list-leaks:n.
 > Running smpirun with -wrapper "valgrind --leak-check=full" can provide more information
-> [0.000000] [smpi_utils/WARNING] Leaked handle of type MPI_Comm
-> [0.000000] [smpi_utils/WARNING] Leaked handle of type MPI_Group
-> [0.000000] [smpi_utils/WARNING] Leaked handle of type MPI_Comm
-> [0.000000] [smpi_utils/WARNING] Leaked handle of type MPI_Group
-> [0.000000] [smpi_utils/WARNING] Leaked handle of type MPI_Comm
-> [0.000000] [smpi_utils/WARNING] Leaked handle of type MPI_Group
-> [0.000000] [smpi_utils/WARNING] Leaked handle of type MPI_Comm
-> [0.000000] [smpi_utils/WARNING] Leaked handle of type MPI_Group
+> [0.000000] [smpi_utils/INFO] To get more information (location of allocations), compile your code with -trace-call-location flag of smpicc/f90
+> [0.000000] [smpi_utils/INFO] Leaked handle of type MPI_Comm
+> [0.000000] [smpi_utils/INFO] Leaked handle of type MPI_Group
+> [0.000000] [smpi_utils/INFO] Leaked handle of type MPI_Comm
+> [0.000000] [smpi_utils/INFO] Leaked handle of type MPI_Group
+> [0.000000] [smpi_utils/INFO] Leaked handle of type MPI_Comm
+> [0.000000] [smpi_utils/INFO] Leaked handle of type MPI_Group
+> [0.000000] [smpi_utils/INFO] Leaked handle of type MPI_Comm
+> [0.000000] [smpi_utils/INFO] Leaked handle of type MPI_Group
 > [0.000000] [smpi_utils/INFO] Memory Usage: Simulated application allocated 128 bytes during its lifetime through malloc/calloc calls.
 > Largest allocation at once from a single process was 16 bytes, at sysdep.h:59. It was called 8 times during the whole simulation.
 > If this is too much, consider sharing allocations for computation buffers.
@@ -24,14 +25,15 @@ $ $VALGRIND_NO_LEAK_CHECK ${bindir:=.}/../../../smpi_script/bin/smpirun -wrapper
 > 
 > [0.000000] [smpi_utils/INFO] Probable memory leaks in your code: SMPI detected 8 unfreed MPI handles : display types and addresses (n max) with --cfg=smpi/list-leaks:n.
 > Running smpirun with -wrapper "valgrind --leak-check=full" can provide more information
-> [0.000000] [smpi_utils/WARNING] Leaked handle of type MPI_Comm
-> [0.000000] [smpi_utils/WARNING] Leaked handle of type MPI_Group
-> [0.000000] [smpi_utils/WARNING] Leaked handle of type MPI_Comm
-> [0.000000] [smpi_utils/WARNING] Leaked handle of type MPI_Group
-> [0.000000] [smpi_utils/WARNING] Leaked handle of type MPI_Comm
-> [0.000000] [smpi_utils/WARNING] Leaked handle of type MPI_Group
-> [0.000000] [smpi_utils/WARNING] Leaked handle of type MPI_Comm
-> [0.000000] [smpi_utils/WARNING] Leaked handle of type MPI_Group
+> [0.000000] [smpi_utils/INFO] To get more information (location of allocations), compile your code with -trace-call-location flag of smpicc/f90
+> [0.000000] [smpi_utils/INFO] Leaked handle of type MPI_Comm
+> [0.000000] [smpi_utils/INFO] Leaked handle of type MPI_Group
+> [0.000000] [smpi_utils/INFO] Leaked handle of type MPI_Comm
+> [0.000000] [smpi_utils/INFO] Leaked handle of type MPI_Group
+> [0.000000] [smpi_utils/INFO] Leaked handle of type MPI_Comm
+> [0.000000] [smpi_utils/INFO] Leaked handle of type MPI_Group
+> [0.000000] [smpi_utils/INFO] Leaked handle of type MPI_Comm
+> [0.000000] [smpi_utils/INFO] Leaked handle of type MPI_Group
 > [0.000000] [smpi_utils/INFO] Memory Usage: Simulated application allocated 128 bytes during its lifetime through malloc/calloc calls.
 > Largest allocation at once from a single process was 16 bytes, at sysdep.h:59. It was called 8 times during the whole simulation.
 > If this is too much, consider sharing allocations for computation buffers.