After the Windows 10 Anniversary Update (1607), I get access violation errors with Visual Leak Detector.
Exception thrown at 0x00007FF8A7B97FE7 (ntdll.dll) in Axxxxxxx4_64.exe: 0xC0000005: Access violation reading location 0x00007FF8A7CD5252.
Module Information on ntdll.dll:
10.0.14393.0 (rs1_release.160715-1616)
I think, it's this line (during base member initialization):
QApplication(argc, argv)
I'm not experienced with VLD. I just started using it few days ago. But it worked fine until the Windows update, so it might be a good guess.
Comments: Finally got around to getting the code to build on my machine. Using v2.5 tag and applying this patch https://github.com/ioannis-e/vld/commit/48d9fef04a3117747c594afaf3036105713323d3 I can confirm x64 works as per x86. I also switch the platform toolset to v140 (instead of v140_xp) as v140_xp doesn't seem to be installed on my system. FYI: Applying the patch onto the master branch resulted in new memory leaks being detected. I'm not sure they're real.
Exception thrown at 0x00007FF8A7B97FE7 (ntdll.dll) in Axxxxxxx4_64.exe: 0xC0000005: Access violation reading location 0x00007FF8A7CD5252.
Module Information on ntdll.dll:
10.0.14393.0 (rs1_release.160715-1616)
I think, it's this line (during base member initialization):
QApplication(argc, argv)
I'm not experienced with VLD. I just started using it few days ago. But it worked fine until the Windows update, so it might be a good guess.
Comments: Finally got around to getting the code to build on my machine. Using v2.5 tag and applying this patch https://github.com/ioannis-e/vld/commit/48d9fef04a3117747c594afaf3036105713323d3 I can confirm x64 works as per x86. I also switch the platform toolset to v140 (instead of v140_xp) as v140_xp doesn't seem to be installed on my system. FYI: Applying the patch onto the master branch resulted in new memory leaks being detected. I'm not sure they're real.