Hi Aleksey, Memory leak seems to have been fixed with your 2nd patch. Strange side affect of the recompile though, my xmlsec command line utility now crashes. Our application works, but the command line utility crashes with the new executables.
I'll check further. Ed -----Original Message----- From: Edward Shallow [mailto:[EMAIL PROTECTED] Sent: May 6, 2006 4:41 PM To: 'Aleksey Sanin' Cc: 'xmlsec@aleksey.com' Subject: RE: [xmlsec] FW: Free/Destroy versus Memory Leak OK link.exe /lib works ... finally got it all compiled and linked. Ran into more "C" runtime problems, but got those resolved as well. I'll write it all up next week, not really that simple when using the free Microsoft downloads ... Now on to tracking down if the memory leak is still there ... Stay tuned ... Thanks again Aleksey, Ed -----Original Message----- From: Aleksey Sanin [mailto:[EMAIL PROTECTED] Sent: May 6, 2006 1:17 PM To: [EMAIL PROTECTED] Cc: xmlsec@aleksey.com Subject: Re: [xmlsec] FW: Free/Destroy versus Memory Leak This is what google says http://www.codecomments.com/archive292-2004-8-262165.html You might need to tweak makefile a little bit. Search for "lib.exe" and replace it with "link.exe /lib" Aleksey Edward Shallow wrote: > .... Getting really close to the end now ;) > > ... Missing lib.exe ??? Not in any of the MS tools I downloaded and > installed ? > > ... Where did you get this exe from ? > > Ed > > lib.exe /nologo /OUT:binaries\libxmlsec-openssl_a.lib > libxmlsec_openssl_a.int\app.obj libxmlsec_openssl_a.int\bn.obj libx > mlsec_openssl_a.int\ciphers.obj libxmlsec_openssl_a.int\crypto.obj > libxmlsec_openssl_a.int\digests.obj libxmlsec_openssl_a.int\ evp.obj > libxmlsec_openssl_a.int\hmac.obj libxmlsec_openssl_a.int\kt_rsa.obj > libxmlsec_openssl_a.int\kw_aes.obj > libxmlsec_opens > sl_a.int\kw_des.obj libxmlsec_openssl_a.int\signatures.obj > libxmlsec_openssl_a.int\strings.obj libxmlsec_openssl_a.int\symkeys. > obj libxmlsec_openssl_a.int\x509.obj > libxmlsec_openssl_a.int\x509vfy.obj > 'lib.exe' is not recognized as an internal or external command, > operable program or batch file. > NMAKE : fatal error U1077: 'lib.exe' : return code '0x1' > Stop. > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Aleksey Sanin > Sent: May 5, 2006 5:44 PM > To: [EMAIL PROTECTED] > Cc: xmlsec@aleksey.com > Subject: Re: [xmlsec] FW: Free/Destroy versus Memory Leak > >> - Got passed the missing "C" runtime stuff, now I am failing on >> openssl-related include's > > You need to set correct OpenSSL version in the mycfg.bat file. E.g. > if you use OpenSSL 0.9.8 then you should have something like this: > > --crypto=mscrypto,openssl=098 > >> P.S. Are the warnings on xmlsec-ltdl.c below OK ? > Yes, I think it is OK. > > Aleksey > > _______________________________________________ > xmlsec mailing list > xmlsec@aleksey.com > http://www.aleksey.com/mailman/listinfo/xmlsec > > > _______________________________________________ > xmlsec mailing list > xmlsec@aleksey.com > http://www.aleksey.com/mailman/listinfo/xmlsec _______________________________________________ xmlsec mailing list xmlsec@aleksey.com http://www.aleksey.com/mailman/listinfo/xmlsec
