[Help-gnutls] Asynchronous application and not enough buffer ready

cascardo at minaslivre.org cascardo at minaslivre.org
Wed Jun 8 21:44:27 CEST 2005

On Wed, Jun 08, 2005 at 03:46:08PM -0300, cascardo at minaslivre.org wrote:
> However, the solution proposed has made gnutls_record_recv go into a
> loop. It should return with 0 bytes read to the caller. I will check
> out the code and see if it's possible. If not, I will have to use some
> solutions I didn't want to.
> On Wed, Jun 08, 2005 at 08:15:58PM +0200, Nikos Mavrogiannopoulos wrote:
> > On Wednesday 08 June 2005 17:16, cascardo at minaslivre.org wrote:
> > 
> > > When the record size is greater than what the application has already
> > > put in the buffer, gnutls asks for bytes to the pull function which
> > > have not yet been read from the socket. To read these bytes, the main
> > > loop must run again. 
> > Then the pull function should return -1 and set errno to EAGAIN.
> > 

In fact, the code really does return when the pull function returns
with EAGAIN errno. However, my pull function gets called before
gnutls_record_recv returns. I will try harder to debug it, although I
may have to build a non-stripped debugging version of gnutls.


Thadeu Cascardo.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: </pipermail/attachments/20050608/5baeffd5/attachment.pgp>

More information about the Gnutls-help mailing list