> Coverity alerted to about 85 memory leaks under Windows. Ominously, it > coincided with the 80 or so objects dumped after running a Debug build > under Visual Studio. >
If I build the library and cryptest projects using nmake with our cryptest.nmake, then I don't see any leaks. Nmake-based builds use mostly the same settings as Visual Studio. That is, I copied nmake CXXFLAGS from VS build log. I then removed things we did not need, like LTCG and creating import libraries. I went deeper and it appears Visual Studio is adding flags we don't specify. For example, from cryptest build log (yes, the test program), there's a link option /IMPLIB:"x64\Output\Debug\cryptest.lib" . However, its not set in the project's property page. Its bizarre, and I cannot find the behavior documented anywhere. I'm think all the leaks are due to Visual Studio. But I can't confirm it until we stop Visual Studio from adding /IMPLIB and some other flags. Does anyone have expertise in VS2010 and above, and setting up projects? Jeff -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. --- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
