Boost logo

Boost :

From: Scott (cheesy4poofs_at_[hidden])
Date: 2006-09-13 10:41:16


Hi Chris,

> > I made the changes you requested and unfortunately things
> > aren't any clearer. What I'm seeing now is error_code ==
> > SSL_ERROR_SYSCALL. However, the line I added above:
> >
> > int sys_error_code = asio::detail::socket_ops::get_error();
> >
> > sys_error_code == 0
>
> I would suggest moving the get_error() line to immediately after
> the primitive_() call, because I suspect something must be
> clearing the error. (Unless the SSL_ERROR_SYSCALL itself is
> misleading and there never really was a system error, but let's
> not go there unless we have to :)

I did as you asked and unfortunately the results are the same.
sys_error_code is still zero, even when I make the call immediately after
the primitive_() call.

Does this imply there's a problem with the underlying ASIO SSL
implementation?

Scott


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk