https://svn.boost.org/trac10/ticket/7553 <p> I am experiencing an issue where trying to access a previously created shared memory segment causes the following exception to be thrown when using the IPC and ASIO (TCP sockets specifically) libraries together: </p> <p> terminate called after throwing an instance of 'boost::exception_detail::clone_impl&lt;boost::exception_detail::error_info_injector&lt;boost::system::system_error&gt; &gt;' </p> <blockquote> <p> what(): resolve: No such host is known </p> </blockquote> <p> This is issue does not occur when I utilize 1.49 libraries. When the shared memory is removed the application does not throw this exception but when subsequently restarted, the exception is thrown. My goal for utilizing the shared memory structure is that it provide a persistence mechanism for a collection of IDs generated by the application that need to be available should a crash happen. Accessing the shared memory at different application instances without creating the socket works as expected (the previously created shared segment is accessible). The exception happens whenever the shared memory segment exists prior to the application start up. Again this does not happen with the verion 1.49 libraries. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/7553 Trac 1.4.3 Todd Chadwick <ctchadwick@…> Mon, 22 Oct 2012 23:54:15 GMT https://svn.boost.org/trac10/ticket/7553 https://svn.boost.org/trac10/ticket/7553 <ul> <li><strong>attachment</strong> → <span class="trac-field-new">test-asio.cpp</span> </li> </ul> Ticket Todd Chadwick <ctchadwick@…> Mon, 22 Oct 2012 23:56:57 GMT https://svn.boost.org/trac10/ticket/7553#comment:2 https://svn.boost.org/trac10/ticket/7553#comment:2 <ul> <li><strong>severity</strong> <span class="trac-field-old">Problem</span> → <span class="trac-field-new">Not Applicable</span> </li> </ul> <p> I have managed to resolve the issue. The problem resided in another piece of code, although I was able to replicate a similar issue with the code I posted, albeit not the same issue. As of my current experiment, I'd say my issue is resolved and appears to be my implementation of the libraries and not something in the libraries. </p> Ticket viboes Fri, 18 Jan 2013 22:58:33 GMT https://svn.boost.org/trac10/ticket/7553#comment:3 https://svn.boost.org/trac10/ticket/7553#comment:3 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">invalid</span> </li> </ul> Ticket