Interesting. I think I see the relevant bit of the code. I am betting
your application has not loaded the DLLs that CryptoPP is looking for
at the time the tests are run ("msvrcrt.dll" or "msvcrt.dll") - which
may be due to you not using those DLLs (due to your project settings),
or due to them being later in the DLL load order. Unfortunately, I
don't know how to control the DLL load order.On Jul 27, 7:17 am, soeren <[EMAIL PROTECTED]> wrote: > Hello Parch, > > > I'm not sure whether CryptoPP::DoDllPowerUpSelfTest() is actually > > called by default when you load the DLL. > > Since you're in Visual Studio, why don't you set a breakpoint on that > > function, and step through the self-test and see where it fails? > > I was not aware of this, good idea. I debugged it in the dlltest which > comes with Crypto++ and it is called and debugged it with my own > program and it is called as well. BUT...while debugging I found that > in the creation of an object in "DoDllPowerUpSelfTest" an exception is > thrown: "Crypto++ was not able to obtain new and delete function > pointers." > > Sorry for that, absolutely no idea why this comes up. I think, still > some quite "secret" project settings are missing. Any ideas for that > problem? > > Thanks again, > Soeren Gerlach --~--~---------~--~----~------------~-------~--~----~ 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. -~----------~----~----~----~------~----~------~--~---
