Christian Parpart wrote:
Hi all,
I'm valgrinding my application since a few days, and also ran into
a file descriptor leak within gnutls_dh_params_generate2();
The following fragment is the backtrace generated by valgrind
at the time of where the file descriptor has been allocated in:
[...]
Well, is there anything I need to call as cleanup routine? Or why is it
holding a link up to /dev/urandom all the runtime over and w/o closing at
shutdown?
As far as I remember this is normal libgcrypt behaviour. Some structures
never get deinitialized. But to be sure I'd suggest to forward your mail
to the libgcrypt-dev list.
Nikos
_______________________________________________
Help-gnutls mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/help-gnutls
