proper init and destruction
vasili3000 at hotmail.com
Tue Jan 29 12:43:39 CET 2008
i am currently debugging a library that uses libgrypt, ver 11.2.3.
running a sample program through valgrind, i noticed that some memory allocated when using function
is never released. the samle program follows:
memset(message, 0, sizeof(message));
int i =0;
gcry_randomize(message, 16, GCRY_VERY_STRONG_RANDOM);
this call uses only once some 1500 bytes that are never released. Is there something I can do about it? am i missing something on proper initialization and destruction of the library internal structures?
also, in some other part of the lib i am debugging, successive calls to
allocate up to 500 bytes that are never released. Do you have any clues on that?
Express yourself instantly with MSN Messenger! Download today it's FREE!
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gcrypt-devel