Memory leaks are observed for libgnutls in multi-thread mode

[tangtong]

Hi,Nikos

The gnutls-cli built by me will core when I enable TLS1.2. I think the code base I use is a little diffent from what you are using. The following is my steps to setup the build enviorment:
1)Download a gnutls releaes package 2.8.3 and decompress it;
2)Download 2.9.4 snap shot and uncompress it to the directory created in the step 1);
3)Run patch you provide.

Seems only snapshot of 2.9.4 is not the whole build env, that's why i decompress it to a build enviorment of 2.8.3.

Regards
Tony








> Date: Thu, 22 Oct 2009 19:31:02 +0300
> From: nmav at gnutls.org
> To: tang__tong at hotmail.com
> CC: simon at josefsson.org; help-gnutls at gnu.org
> Subject: Re: Memory leaks are observed for libgnutls in multi-thread mode
> 
> tangtong wrote:
> > Hi,Nikos
> 
> > 2)The patch doesn't support
> > "NONE:+VERS-TLS1.2:+AES-256-CBC:+RSA:+SHA256:+COMP-NULL", I think your
> > patch disable the tls1.2 support, it will core with the following dump
> > info:
> >  fe9a2bb8 _gcry_md_copy (ffbff33c, 0, 0, febc6ed0, 14f8, fed3805c) + 4
> >  feca8dfc _gnutls_hash_copy (ffbff338, 365c4, 0, 0, 0, 0) + 80
> >  fec9e0fc _gnutls_finished (36180, 2, ffbff440, 1, 6, 0) + 84
> >  fec9edc0 _gnutls_send_handshake_final (0, 0, 0, e, e, 4) + 128
> >  feca2548 _gnutls_handshake_common (36180, 0, 10, 4, ffffffe0, ffbff551) + 30
> >  feca382c gnutls_handshake (0, 4, 32fc8, 8e8, 17ac, ffbff5c4) + 60
> >  000119bc main     (1, ffbffa54, ffbffa5c, 22508, 0, 0) + 118
> >  000112c8 _start   (0, 0, 0, 0, 0, 0) + 5c
> 
> Can you send me information on how I can reproduce this issue? I can use
> ./gnutls-cli tls.secg.org --priority
> "NONE:+VERS-TLS1.2:+AES-128-CBC:+RSA:+DHE-DSS:+SHA256:+COMP-NULL" to
> connect using TLS1.2 without any issues.
> 
> regards,
> Nikos
 		 	   		  
_________________________________________________________________
全新 Windows 7：寻找最适合您的 PC。了解详情。
http://www.microsoft.com/china/windows/buy/ 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20091023/0f0d42a4/attachment.htm>