Re: [Boost-users] boost::asio destructor segfault?

Sean McAllister wrote:

Hmmm, I've only got the one extra thread to run the asynchronous event loop in. If I have async_read events outstanding, wouldn't the above code cause my destructor to block until I've read another message (which may happen quite infrequently)?

That's right -- but you still would like to have all operations finished before the end of the destructor. If you need to close sockets, call, e.g., socket::close. Cheers, Rutger