Most of the Crypto++ examples invoke "new" inside a constructor call, which doesn't allow a corresponding "delete" to be called. Does this cause a memory leak?
Example: StringSource(pMessage, nMessageSize, true, newStreamTransformationFilter(aes, newStringSink(sEncryptedSegment))); The code above works, but I was unsure about a memory leak, so I tried putting things on the stack: StringSinkoSink(sEncryptedSegment); StreamTransformationFilteroFilter(aes, &oSink); StringSource(pMessage, nMessageSize, true, &oFilter); The revised code crashes with a segmentation fault. Is there a memory leak with the first form above? If so, how should it be revised to avoid that? Thanks. Rod -- 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.
