gnutls_record_check_pending() returning non-0 but gnutls_record_recv() gives no data

[Nikos Mavrogiannopoulos]

On Tue, Apr 10, 2012 at 12:40 AM, Wilmer van der Gaast <wilmer at gaast.net> wrote:

> Yes, this works better:
> 0x995d30 gnutls_record_recv = -28
> 0x995d30 gnutls_record_check_pending = 0
> 2 ASSERT: gnutls_buffers.c:510
> 2 ASSERT: gnutls_record.c:1000
> 2 ASSERT: gnutls_record.c:1202
> 0x995d30 gnutls_record_recv = -28
> 0x995d30 gnutls_record_check_pending = 0
> 0x995d30 gnutls_record_recv = 2048
> 0x995d30 gnutls_record_check_pending = 8770
> 0x995d30 gnutls_record_recv = 2048
> 0x995d30 gnutls_record_check_pending = 6722
> 0x995d30 gnutls_record_recv = 2048
> I'm getting my data now, without ending up in an almost infinite loop. Thank
> you!
> Would you be able to tell me which versions of GnuTLS are affected by this
> by the way? I'm thinking of adding a work-around so BitlBee will still work
> properly with affected GnuTLS versions.

This "feature" was added in 3.0.13.

regards,
Nikos