Any thoughts on this crash ?

Thanks,
Walt.

On Dec 10, 7:49 am, Walter Villalba <[email protected]> wrote:
> I've been using crypto++ in one of my apps for a couple years now and had
> never experienced a crash within the library until now.  I bumped up the
> encryption a few weeks ago from 128-bits to 256-bits and ran quite a few
> tests without any issues.  Now I need to deal with this crash, which
> happened only once so far, and might be very difficult to reproduce.
>
> My setup:
> * Windows XP Pro SP 3
> * MS VS 2008 (VC9) SP 1
> * Crypto++ 5.5.2 - AES, CFB mode, 128 and 256 bit key.
>
>     Crash info:        Unhandled exception Access Violation (0xc0000005) at
> 0x7C910A19.
>     Process:           C:\Program Files\XXX\MyProgram.exe
>     Stack trace:
>  (0) : ntdll.dll at wcsncpy().
>  (0) : ntdll.dll at wcsncpy().
>  (0) : MSVCR90.dll at free().
>  (0) : MyModule.dll at CryptoPP::StreamTransformationFilter::`scalar
> deleting destructor''().
>  (0) : MyModule.dll at CryptoPP::StringSource::~StringSource().
> e:\MyDevWorkspace\MyModule\AESEncryptor.cpp(514) : MyModule.dll at
> AESEncryptor::decrypt().
>
> This is the code where it crashed:
>
>         try {
> StringSource( msg, msgLen, true,
> new StreamTransformationFilter( *pAESDecryptor,
> new StringSink( plainText )
> ) // StreamTransformationFilter
> ); // StringSource
>
> } // end-try
>
> I'm wondering if this could be a bug in the Crypto++ v5.5.2 library,
> since *version
> 5.6.1 has a few bug fixes for the AES algorithm.*   Any help would be very
> much appreciated, since this app is running in the field already so I need
> to find out the root cause ASAP.
>
> Thanks,
> Walt.

-- 
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.

Reply via email to