gnutls_bye() error handling in a sane way

Jos Kuijpers jos at
Fri Jan 7 22:34:50 CET 2011


Since a week, I am having serious problems with the GnuTLS library
concerning the gnutls_bye():

I am writing a binding between gnutls and ObjFW
( =>
When an attempt to reading from the socket failed, and results in a closed
socket (because of a malicious client, or lost network connection, etc),
the close method of the object gets called. This method then will call
gnutls_bye, socket close and gnutls_deinit.

There is the problem. Gnutls_bye sends data. When the socket is broken, and
gnutls_bye is called, my program DIES: SIGPIPE.
I am very disappointed about this. Catching signals in a library is

Is there a way to get proper error handling done in this case?
Else, I will send this mail to the development mailing list for adding
support for sane error handling.

With kind regards,


More information about the Gnutls-help mailing list