Check the Bounds Checker KB articles. I recall articles from years ago
stating that BC calls them leaks because the objects are destroyed after the
program terminates (nature of using the runtime).
I'd grep myself, but DSL tanked and I'm on dialup.
----- Original Message -----
From: "James Vanns" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, June 20, 2005 7:17 AM
Subject: RE: Memory Leak
This is quite alarming. Does anyone have any indication as to [exactly]
where the memory leak(s) is/are? I also have code (going live date
approaching) that uses Crypto++' RSASS implementation.
Jim
On Wed, 2005-06-15 at 08:53 +0800, ZENG Ke wrote:
I have the same observation, cryptopp causes severe memory leak.
> -----Original Message-----
> From: Newman, Christofer [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, June 15, 2005 8:48 AM
> To: [email protected]
> Subject: RE: Memory Leak
>
> From what I've been able to tell, that's exactly where the memory leak
> is. We've had to stop using cryptopp for signing and verification. I've
> posted twice asking for help. I hope you have beter luck. I'll be
> watching the board.
>
> -Chris
>
> -----Original Message-----
> From: Seshu Madabushi [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 14, 2005 3:33 PM
> To: [email protected]
> Subject: Memory Leak
>
> All
>
> I am using cryptopp.dll (FIPS version) to do signing and verification
> process. When debugging my application through Bounds Checker I noticed
> that memory leaks. Below is the code snippet I am using for signing.
> Can
> anyone please explain whether the leak is in CryptoPP?
>
> StringSource privFile(prvkey1,len,true, NULL);
> RSASSA_PKCS1v15_SHA_Signer priv(privFile);
> priv.SignMessage(GlobalRNG(),
> (byte *) DigestValue, TotDigestLen , (byte *) signature);
>
> Thanks
> Seshu
>
--
James Vanns BSc (Hons) MCP
Linux Systems Administrator
Software Engineer (Linux / C & C++)
Canterbury Christ Church University College
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x24045370
