https://svn.boost.org/trac10/ticket/12221 <p> According to coroutine2 docs: "In contrast to coroutine&lt;&gt;::pull_type, instantiating an coroutine&lt;&gt;::push_type does not pass the control of execution to coroutine-function - instead the first call of coroutine&lt;&gt;::push_type::operator() synthesizes a complementary coroutine&lt;&gt;::pull_type and passes it as reference to coroutine-function. " </p> <p> So the function of a push-coroutine should never be entered unless at least one value is pushed. But the coroutine always tries to unwind in destructor and mistakenly resumes the function. Example attached. </p> <p> This bug is present in coroutine2. Original coroutine library is unaffected. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/12221 Trac 1.4.3 valentin.milea@… Sun, 22 May 2016 09:16:09 GMT https://svn.boost.org/trac10/ticket/12221 https://svn.boost.org/trac10/ticket/12221 <ul> <li><strong>attachment</strong> → <span class="trac-field-new">coro2_unwind_bug.cpp</span> </li> </ul> Ticket olli Sun, 22 May 2016 15:38:45 GMT https://svn.boost.org/trac10/ticket/12221#comment:2 https://svn.boost.org/trac10/ticket/12221#comment:2 <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">fixed</span> </li> </ul> Ticket