I found it.
Using "step" in gdb showed that the new calls that valgrind complains about
go into.... qtwebengine/src/3rdparty/chromium/base/allocator/allocator_shim.cc
146├>void* ShimCppNew(size_t size) {
147│ const allocator::AllocatorDispatch* const chain_head = GetChainHead();
148│ void* ptr;
149│ do {
150│ ptr = chain_head->alloc_function(chain_head, size);
151│ } while (!ptr && CallNewHandler());
152│ return ptr;
153│ }
Indeed chromium's allocator_shim_override_cpp_symbols.h says
SHIM_ALWAYS_EXPORT void* operator new(size_t size)
SHIM_ALIAS_SYMBOL(ShimCppNew);
This is why it didn't happen in smaller testcases, it only happens when
including some qtwebengine headers.
=> No valgrind bug, sorry for the noise. I am now going to yell at the
qtwebengine/chromium people for polluting applications with their custom
operator new...
--
David Faure, fa...@kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
