Can you post this like the twenties time? I really helps to find the problem.
If you cannot help in getting closer to the solution, you've done everything by making _one_ report to the list. It won't be faster if you report it every 45 minutes. Viktor On 2010 May 15, at 21:54, Fernando Athayde wrote: > bur Przemek look this: > E:\harbour_cvs\contrib\hbtip\tests>hbmk2 gmail.prg hbtipssl.hbc > hbmk2: Processando script local: hbmk.hbm > hbmk2: Processando arquivo de configuração: e:\harbour_gcc\bin\hbmk.cfg > hbmk2: Processando: hbtipssl.hbc > Harbour 2.1.0beta1 (Rev. 14471) > Copyright (c) 1999-2010, http://www.harbour-project.org/ > Compiling 'gmail.prg'... > Lines 196, Functions/Procedures 1 > Generating C source output to > 'C:\Users\athayde\AppData\Local\Temp\gmail.c'... D > one. > Info: resolving _SSL_CIPHER_get_version by linking to > __imp__SSL_CIPHER_get_vers > ion (auto-import) > E:\mingw\BIN\..\lib\gcc\mingw32\3.4.5\..\..\..\..\mingw32\bin\ld.exe: > warning: a > uto-importing has been activated without --enable-auto-import specified on > the c > ommand line. > This should work unless it involves constant data structures referencing > symbols > from auto-imported DLLs. > > E:\harbour_cvs\contrib\hbtip\tests>gmail > > .T. > > E:\harbour_cvs\contrib\hbtip\tests> > E:\harbour_cvs\contrib\hbtip\tests> > E:\harbour_cvs\contrib\hbtip\tests>hbmk2 -mt gmail.prg hbtipssl.hbc > hbmk2: Processando script local: hbmk.hbm > hbmk2: Processando arquivo de configuração: e:\harbour_gcc\bin\hbmk.cfg > hbmk2: Processando: hbtipssl.hbc > Harbour 2.1.0beta1 (Rev. 14471) > Copyright (c) 1999-2010, http://www.harbour-project.org/ > Compiling 'gmail.prg'... > Lines 196, Functions/Procedures 1 > Generating C source output to > 'C:\Users\athayde\AppData\Local\Temp\gmail.c'... D > one. > Info: resolving _SSL_CIPHER_get_version by linking to > __imp__SSL_CIPHER_get_vers > ion (auto-import) > E:\mingw\BIN\..\lib\gcc\mingw32\3.4.5\..\..\..\..\mingw32\bin\ld.exe: > warning: a > uto-importing has been activated without --enable-auto-import specified on > the c > ommand line. > This should work unless it involves constant data structures referencing > symbols > from auto-imported DLLs. > > E:\harbour_cvs\contrib\hbtip\tests>gmail > > .F. > > Best Regards, > Fernando Athayde > > De: Przemysław Czerpak <dru...@acn.waw.pl> > Para: Harbour Project Main Developer List. <harbour@harbour-project.org> > Enviadas: Sábado, 15 de Maio de 2010 16:39:27 > Assunto: Re: Res: Res: [Harbour] tipclientsmtp problem with MT > > On Sat, 15 May 2010, Fernando Athayde wrote: > > Hi, > > > Przemek, i was think, may be problem is the multithread support of openssl > > dll´s > > i was trying build openssl, but without success > > If non HVM thread tries to access HVM, i.e. to execute some .prg code > then it simply GPF so I do not think it's the source o your problem. > > > but if you test gmail.prg with -MT you´ll see the problem > > Both MT and ST versions returns .T. so they seem to work but > valgrind produces for both of them 285KB log with 336 errors: > Conditional jump or move depends on uninitialised value(s) > inside low level SSL code so there is sth wrong with SSL library > or rather with Harbour wrapper to this library (hbssl) and this > may cause any unpredictable results depending on values in > uninitialised memory. Probably in your MT builds this memory > contains data which breaks communication process. > > > best regards, > Przemek > _______________________________________________ > Harbour mailing list (attachment size limit: 40KB) > Harbour@harbour-project.org > http://lists.harbour-project.org/mailman/listinfo/harbour > > _______________________________________________ > Harbour mailing list (attachment size limit: 40KB) > Harbour@harbour-project.org > http://lists.harbour-project.org/mailman/listinfo/harbour _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
