[gnutls-help] Issues with both gnutls 3.3.0 and 3.3.1

Nikos Mavrogiannopoulos nmav at gnutls.org
Mon Apr 28 17:25:13 CEST 2014

On Mon, Apr 28, 2014 at 4:49 PM, Martin Kletzander <mkletzan at redhat.com> wrote:
>> On a second read, I don't quite understand what is the issue you're having
>> there. Is it that you do a fork-then-exec, and you see the urandom
>> descriptor
>> open? If you simply do a fork that is expected as the child inherits all
>> the
>> open descriptors.
> It happens with usual fork-then-exec on some binaries.  I'm saying
> some because I was not able to identify which ones as it doesn't
> happen for every one.
> I saw this error when running libvirt test suite (make check) where we
> have one test checking that we leak no file descriptors into our
> executed code (apart from other things).  However, even if I run that
> command we are using [1] from shell, it still has these two FDs open.
> The program just creates a log file with all its file descriptors,
> environment data, etc.
> If there's anything I can do to help find the bug, let me know.

I could not reproduce it with a program that calls gnutls_global_init() and
then forks and execs. Is there a way to reproduce it with libvirt tools?


More information about the Gnutls-help mailing list