Re: [Boost-users] asio problem

the actual problem is this: sometimes, after a socket is deleted, instead of oustanding read/write operations returning with asio::error::operation_aborted, they return with no error (error==0), but with socket.native() equal to -1.

Those operations probably had completed *just before* you closed the socket...