16 Jun
2014
16 Jun
'14
2:05 a.m.
On Sunday, June 15, 2014 08:17 PM, Bjorn Reese wrote:
On 06/12/2014 01:18 PM, higashiyama@ncad.co.jp wrote:
ip::tcp::socket::remote_endpoint sometime throws boost::system::system_error exception (error message is "remote_endpoint: Transport endpoint is not connected"). But async_connect is successfully completed. Why does remote_endpoint function throw exception?
Sounds similar to this bug report (although it refers to a newer version of Boost)
Quite. I can't say for sure whether it was working on 1.49 or not, but it looks like I was using async_connect back at that time and only noticed the regression at 1.54. Ben