Hi Folks, We're using the FIPS version of Cryptopp under x64 and have been running into a problem with stack/heap corruption. It usually happens when exiting a thread, although we can usually the application to crash out completely if we simply make a call to LogonUser() as the very first line in the main() application. It will crash out with a null address.
My hunch is that it has something to do with the GetNewAndDeleteForCryptoPP and SetNewAndDeleteforCryptoPP calls but i'm not quite sure. Running the same application in 32 bit runs fine. Has anyone seen anything like this? Thanks Michael -- 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.
