gnutls_handshake() thread problem

Nikos Mavrogiannopoulos nmav at
Wed Nov 17 12:45:04 CET 2010

I don't understand what the problem is there. Do you call
gnutls_handshake in parallel from different threads? In that case
using a mutex is the right thing. We don't support concurrent
execution of gnutls_handshake from parallel threads for the same


On Wed, Nov 17, 2010 at 9:54 AM, Jay Anra <jay.janra at> wrote:
> On 21 Oct I reported a problem I was having with inconsistent errors that
> appeared to be connected with libgcrypt and asynchronous sockets.
> It turns out the problem was not specifically libgcrypt but
> gnutls_handshake().
> What was happening was that the socket interrupt was calling
> gnutls_handshake() with a response from the server, interrupting the
> previous call to gnutls_handshake() that had not yet returned. The interrupt
> call to gnutls_handshake() obviously conflicting with the previous
> incomplete call to gnutls_handshake() and causing all sorts of inconsistent
> errors.
> I have used a mutex to protect gnutls_hansdshake() and the problems have
> gone away.
> Would it be possible to build protection into the library for this?
> _______________________________________________
> Help-gnutls mailing list
> Help-gnutls at

More information about the Gnutls-help mailing list