Hello Pieter, Thank you for your reply. I found your commit changes related to this bug fix (
https://github.com/nzmsv/libzmq/commit/82c06e4417795ebc3e7760af6b02a3d9fd895da6#diff-0), and I can try to pull this change into the 2.2 branch. Looking at the 2.2 vs. 3.2 version, I believe your change would have been done in the xrep.cpp xrep_t::xrecv function in 2.2. There are some major differences that would make backporting the change a little tricky. For example, in 2.2, the zmq_msg_t looks like it's a just a plain C struct, but in 3.2, it looks like it has some methods defined on it (e.g: msg_->size() call). Do you have any tips/advice on being able to properly backport the change? Thank you, Wen Qi Date: Thu, 7 Jun 2012 18:00:56 -0700 From: Pieter Hintjens <[email protected]> Subject: Re: [zeromq-dev] Fixing Socket Problem on ZMQ Version 2.2 To: ZeroMQ development list <[email protected]> Content-Type: text/plain; charset=ISO-8859-1 Wen, Do you want to try backporting the fix to 2.2? It was not very complex, as far as I remember. I fixed the code to simply reject the duplicate identity and generate a random one for the second socket. If you feel like making this change to 2.2, we need a test case and a pull request. -Pieter On Thu, Jun 7, 2012 at 2:22 PM, Wen Qi Chin <[email protected]> wrote: > Hello, > > I am currently using zmq version 2.2, and would like to fix a problem which > causes crashes when two sockets connect with the same identity (see > https://zeromq.jira.com/browse/LIBZMQ-325?for details). This issue seems to > have been resolved in version 3.2, but because there are many significant > API changes between 2.2 and 3.2, I will not be able to easily upgrade my zmq > version to pick up the fix. Does anyone know of an easy way to fix this > problem?on 2.2 instead? > > Thank you >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
