I am trying to update from 4.1.x to 4.2.0 for my project, and when I run it
linked to the 4.2.0 library, I get a stack overflow in a ZeroMQ background
thread when I bind a socket:

 

MyProgram.exe!__chkstk() Line 117

MyProgram.exe!std::map<unsigned
short,zmq::select_t::family_entry_t,std::less<unsigned
short>,std::allocator<std::pair<unsigned short const
,zmq::select_t::family_entry_t> > >::operator[](const unsigned short &
_Keyval) Line 191

MyProgram.exe!zmq::select_t::add_fd(unsigned __int64 fd_, zmq::i_poll_events
* events_) Line 77

MyProgram.exe!zmq::socket_base_t::start_reaping(zmq::select_t * poller_)
Line 1312

MyProgram.exe!zmq::reaper_t::process_reap(zmq::socket_base_t * socket_) Line
128

MyProgram.exe!zmq::object_t::process_command(zmq::command_t & cmd_) Line 135

MyProgram.exe!zmq::reaper_t::in_event() Line 98

MyProgram.exe!zmq::select_t::loop() Line 318

MyProgram.exe!zmq::select_t::worker_routine(void * arg_) Line 393

MyProgram.exe!thread_routine(void * arg_) Line 47

msvcr110d.dll!_callthreadstartex() Line 354

msvcr110d.dll!_threadstartex(void * ptd) Line 337

kernel32.dll!00007ffd243013d2()               Unknown

ntdll.dll!00007ffd246054e4()       Unknown

 

The executable has done nothing but create the context, create the socket,
set a few socket options, and then calls zmq_bind on it. The issue does not
happen in the main thread, and the main thread does not report any errors or
have any faults. No other client is running on this or any networked machine
that is trying to connect to the process yet.

 

I am using MSVC 2012. Stack size is at the default.

 

Any ideas of where I can look to resolve this? I would like to use the
current version of the library, if possible. Thank you,

-robin

 

Robin Scher  |  +1 (213) 448-0443  |   <mailto:ro...@uberware.net>
ro...@uberware.net  |   <http://www.uberware.net/> www.uberware.net

 

_______________________________________________
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev

Reply via email to