Hello,
I'm trying to leak-check a Plugin dll I wrote. The issue I get looks a lot like discussion:224047 and discussion:266691.
I'm using: 2.3, compiled in Release Mode, using dbghlp.dll that comes with windows 8.1. VLD is directly added as a subproject in my solution, it gets build as a static lib and linked directly into my dll.
After a few first troubles of google::protocolbuffers being initialized first (and by that using new-operators from vld with vld not even being initialized), I inserted
Now comes the infinite loop: the call
creates the infinite loop, as somehow this call produces another call to
Any idea how to fix this? Any more information I should provide?
Cheers,
Stefan
I'm trying to leak-check a Plugin dll I wrote. The issue I get looks a lot like discussion:224047 and discussion:266691.
I'm using: 2.3, compiled in Release Mode, using dbghlp.dll that comes with windows 8.1. VLD is directly added as a subproject in my solution, it gets build as a static lib and linked directly into my dll.
After a few first troubles of google::protocolbuffers being initialized first (and by that using new-operators from vld with vld not even being initialized), I inserted
#pragma init_seg (compiler)
into Line #60 of vld.cpp - then it works: the vld instance is initialized first.Now comes the infinite loop: the call
attachToLoadedModules(newmodules);
in vld's cTor, indirectly calls _HeapAlloc
. Inside _HeapAlloc
the first line of codeLPVOID block = HeapAlloc(heap, flags, size);
creates the infinite loop, as somehow this call produces another call to
_HeapAlloc
.Any idea how to fix this? Any more information I should provide?
Cheers,
Stefan