gnutls-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gnutls-dev] gnutls-0.8.4 valgrind diagnosis


From: Ian Peters
Subject: Re: [gnutls-dev] gnutls-0.8.4 valgrind diagnosis
Date: Wed Mar 12 15:11:02 2003

On Tue, 2003-03-11 at 08:25, Rupert Kittinger wrote:
> ==31365== Conditional jump or move depends on uninitialised value(s)
> ==31365==    at 0x402BE756: gcry_mpi_print (mpicoder.c:482)
> ==31365==    by 0x40297AD7: sexp_sscan (sexp.c:1033)
> ==31365==    by 0x40297FA2: gcry_sexp_build (sexp.c:1180)
> ==31365==    by 0x4025C76B: ??? (gnutls_pk.c:516)
> ==31365==    by 0x4025C084: ??? (gnutls_pk.c:124)
> ==31365==    by 0x4025B3A9: ??? (auth_rsa.c:309)
> ==31365==    by 0x402569A2: ??? (gnutls_kx.c:183)
> ==31365==    by 0x40253E1E: ??? (gnutls_handshake.c:1978)
> 
> - - the unitialized memory errors in libgcrypt gcry_mpi_print() seem to be 
> caused by passing an uninitialized size_t in *nbytes.

I actually just sent a patch for this to the libgcrypt mailing list last
night.

Ian




reply via email to

[Prev in Thread] Current Thread [Next in Thread]