You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is the issue that was traced down in #29. I encountered it today again with another application. Because #29 was originally not about this problem, and you closed it meanwhile anyway, I'm opening a new one.
Problem: When dynamically linking against the RELEASE version of the Boost Fiber shared library, compilation and linking are successful, but when the binary is run, it fails.
The problem occurs with the "official" Boost Fiber Asio examples, and also with two different applications of mine.
When dynamically linking against the debug shared library, or statically linking against either the debug or release static library, everything works.
Note: I have tested this only with code using Asio. I don't know if the issue affects non-Asio Fibers code.
Hi Oliver,
This is the issue that was traced down in #29. I encountered it today again with another application. Because #29 was originally not about this problem, and you closed it meanwhile anyway, I'm opening a new one.
Problem: When dynamically linking against the
RELEASE
version of the Boost Fiber shared library, compilation and linking are successful, but when the binary is run, it fails.The problem occurs with the "official" Boost Fiber Asio examples, and also with two different applications of mine.
When dynamically linking against the
debug
shared library, or statically linking against either thedebug
orrelease
static library, everything works.Note: I have tested this only with code using Asio. I don't know if the issue affects non-Asio Fibers code.
Environment: Ubuntu 14.04 64-bit, GCC 4.9.2, latest Modular Boost, latest Boost Fiber (
develop
) branchTo reproduce it with the official examples:
cd /modboost-folder/libs/fiber/examples
debug
build:./echo_server 1234
, in another./echo_client 127.0.0.1 1234
release
build./echo_server 1234
, in another./echo_client 127.0.0.1 1234
The text was updated successfully, but these errors were encountered: