> 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.
>
> I've got it tracked down to this pattern. It appears MSC compilers a not
> generating the call to a destructor:
>
> // Header file
> static const & Integer& Integer::Zero();
>
> // Source file
> static const & Integer& Integer::Zero()
> {
> return Singleton<Integer>().Ref();
> }
>
Most of this was right, but I was wrong about clearing the reported leak.
My script was mis-counting things. The leak remained.
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.
