Skip to content
This repository has been archived by the owner on Jun 12, 2018. It is now read-only.

exception thrown in server start (boost related) #78

Open
artemtarassov opened this issue Aug 4, 2017 · 4 comments
Open

exception thrown in server start (boost related) #78

artemtarassov opened this issue Aug 4, 2017 · 4 comments

Comments

@artemtarassov
Copy link

I'm using boost 1_62, windows 10, running with VS 2013, deploy to win32.
When i do server.start(), the exception below is thrown.
boost_socket_acceptor.hpp: boost::system::error_code ec; this->get_service().open(this->get_implementation(), protocol, ec); boost::asio::detail::throw_error(ec, "open");
My code is just the server implementation. nothing else.
Client implementation works fine btw., i just can't make the server start.
Do you have any ideas?

@eidheim
Copy link
Owner

eidheim commented Aug 5, 2017

Have you tried the v1.3.1 release? I'm curious if I have done some changes since the v1.3.1 release that have broken MSVC compilation somehow.

@eidheim
Copy link
Owner

eidheim commented Aug 5, 2017

Also, does the ws_examples.cpp work? It might be that you are using a different port than 8080? Some ports might need administrator rights to bind to I guess.

@artemtarassov
Copy link
Author

artemtarassov commented Aug 5, 2017

I tried v1.31, tried boost 1_61, other ports, tried with VS 2015, and tested it on another machine runnig windows7. still have the problem.
Maybe it's somehow related to VS or some other settings. Any ideas?
I was not able to compile the tests, there were several linking errors, so i gave up. However, the client implementation works fine.
Here is the crash btw.:
screen shot 2017-08-05 at 20 35 10

@eidheim
Copy link
Owner

eidheim commented Aug 11, 2017

Not sure what to do here as I do not use Windows. But it seems to be a boost on Windows issue if I'm not mistaken. Could it be the way you install boost?

The tests does not compile with MSVC, since MSVC is missing option to turn off access control (gcc/clang's -fno-access-control). In the future though, I see no reason why not to use clang on Windows, that is, when clang is stable for Windows.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants