It is not really hard coded in signaler.cpp, in signaler.cpp it is used to check which mutex to use to lock the port from other zeromq applications. On Aug 21, 2015 3:04 AM, "Matt Bolger" <[email protected]> wrote:
> Brilliant! This hard codded port is the culprit. > > I'd tested this on two machines but turns out both are running RealVNC > which uses port 5905 for its server. > > Also found that this value is hard coded in signaler.cpp in addition to > config.hpp > > So the next question, shouldn't this port being in use be handled more > gracefully? Something for me to raise as a GitHub issue I guess? > > Thanks > Matt > > On Thu, Aug 20, 2015 at 10:24 PM, KIU Shueng Chuan <[email protected]> > wrote: > >> Could you try editing src/config.hpp, change the line signaler_port from >> 5905 to 0 and recompile? >> On 20 Aug 2015 14:13, "Matt Bolger" <[email protected]> wrote: >> >>> Some further digging in case this mean something to someone: >>> >>> I *think* the issue can be traced back to zmq::signaler_t::make_fdpair() >>> - line 447 >>> >>> rc = bind (listener, (const struct sockaddr*) &addr, sizeof addr); >>> >>> this fails with error 10030 (WSAEACCES) >>> >>> >>> https://msdn.microsoft.com/en-us/library/windows/desktop/ms740668(v=vs.85).aspx#WSAEACCES >>> >>> So make_fdpair() in the signaler_t constructor never produces anything >>> other than invalid file descriptors. This seems to go through without >>> anything saying this is an issue until these descriptors are passed to >>> select() for the first time. >>> >>> >>> On Thu, Aug 20, 2015 at 4:00 AM, Bob Clarke <[email protected]> >>> wrote: >>> >>>> I have two projects using 0MQ. I built 4.1.2 from source but, frankly, >>>> didn't run all the test programs. My apps are simple (PUB/SUB, REQ/REP, >>>> PAIR and PUSH/PULL) and have only encountered one problem with PAIR >>>> sockets, which may be of my own doing. >>>> >>>> Bob >>>> >>>> On Tue, Aug 18, 2015 at 6:08 PM, Matt Bolger <[email protected]> >>>> wrote: >>>> >>>>> Hi All, >>>>> >>>>> >>>>> >>>>> Anyone out there successfully building/using ZeroMQ under Windows >>>>> (MSVC)? >>>>> >>>>> >>>>> >>>>> I'm trying to build/use the current master in GitHub ( >>>>> https://github.com/zeromq/libzmq) which has Visual Studio projects as >>>>> well as CMake files. I've built the CMake project (after fixing an issue >>>>> in >>>>> the MSVC specific stuff - https://github.com/zeromq/libzmq/issues/1517) >>>>> which also builds all the tests but the tests fail the same way my simple >>>>> test program does. >>>>> >>>>> >>>>> >>>>> The first call to WinSock select() always results in WSAENOTSOCK and >>>>> the app bails. I've now tried this on a 64bit Win7 and Win8 machines with >>>>> both VS2010 and VS2013 for debug and release builds with no luck :( >>>>> >>>>> >>>>> >>>>> I get similar aborts when trying to build against the pre-built >>>>> binaries on the ZeroMQ site or building my own with the included Visual >>>>> Studio project files included in the repository. >>>>> >>>>> >>>>> >>>>> Maybe I'm missing something obvious but any help would be great. >>>>> >>>>> >>>>> Thanks >>>>> >>>>> Matt >>>>> >>>>> _______________________________________________ >>>>> zeromq-dev mailing list >>>>> [email protected] >>>>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> zeromq-dev mailing list >>>> [email protected] >>>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev >>>> >>>> >>> >>> _______________________________________________ >>> zeromq-dev mailing list >>> [email protected] >>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev >>> >>> >> _______________________________________________ >> zeromq-dev mailing list >> [email protected] >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> >> > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
