Here is an extract of the valgrind session :

[... zillions of error reports ...]

==103518== Conditional jump or move depends on uninitialised value(s)
==103518==    at 0xD95C49B: ???
==103518==    by 0x2108005F: ???
==103518==
==103518==
==103518== More than 1000 different errors detected.  I'm not reporting any
more.
==103518== Final error counts will be inaccurate.  Go fix your program!
==103518== Rerun with --error-limit=no to disable this cutoff.  Note
==103518== that errors may occur in your program without prior warning from
==103518== Valgrind, because errors are no longer being displayed.
==103518==

(bookworm)ericdegenetais@NXQLX080:~/projects/ANS/mon-profil-psc$ ==103518==
==103518== HEAP SUMMARY:
==103518==     in use at exit: 804,712,204 bytes in 422,561 blocks
==103518==   total heap usage: 20,213,493 allocs, 19,790,932 frees,
2,718,634,561 bytes allocated
==103518==
==103518== LEAK SUMMARY:
==103518==    definitely lost: 4,440,573 bytes in 39,876 blocks
==103518==    indirectly lost: 761,254,808 bytes in 46,509 blocks
==103518==      possibly lost: 13,932,553 bytes in 1,028 blocks
==103518==    still reachable: 24,246,942 bytes in 328,376 blocks
==103518==         suppressed: 0 bytes in 0 blocks
==103518== Rerun with --leak-check=full to see details of leaked memory
==103518==
==103518== Use --track-origins=yes to see where uninitialised values come from
==103518== For lists of detected and suppressed errors, rerun with: -s
==103518== ERROR SUMMARY: 1000 errors from 1000 contexts (suppressed: 0 from 0)

[1]+  Fini                    valgrind gitg