Hi Enrico
agreed from my point of view 
… It was working before hand (g++ 5.1.1), it is still working now (g++ 7.1.1) but it is complaining a lot…
Our platform is developped in a continuous integration using Cdash so every day we have several constructions/tests/coverage/mem leak checks. I’d like to understand these lines and be able to remove them without having to mask them through a valgrind-suppress file (their number is not constant so it is quite hard to monitor if we add more mem leak on top 
).
If anyone has an idea of what i’m doing that coulb be considered dangerous ( Conditional jump or move depends on uninitialised value(s) )
cheers
jb