Discussion:
[asio-users] Strange Behavior
Hei Chan
2014-04-08 06:28:50 UTC
Permalink
Hi,

I am using boost 1.47.0

I am using a third party library that uses boost ASIO.

For some reason, I see the memory address of boost::asio::detail::task_io_service::outstanding_work_ (which is boost::asio::detail::atomic_count) is changed.

In one particular instance, it is changed from 0x9ea200 (this address is observed in boost::asio::detail::task_io_service's constructor) to 0x9ea1fc (this address is observed in boost::asio::detail::task_io_service::run()) inside the same boost::asio::detail::task_io_service instance (address of 0x9ea190).

How can it be?


Any suggestion?

Thanks in advance.

Loading...