Hello, I can now confirm that the bug is fixed on my side. If pieter's test case works as well, then we can say it's solved I guess. Thanks a lot,
On Wed, May 1, 2013 at 4:10 PM, Victor Perron <[email protected]> wrote: > Thanks a lot for this. Was an easiest fix than I thought :) > Well, I can't test it *right away* (no access to the 3g dongle anymore) > but I'll send you updates asap. > > > On Wed, May 1, 2013 at 3:50 PM, Trevor Bernard > <[email protected]>wrote: > >> I've back ported the fix here and submitted a pull request: >> >> https://github.com/trevorbernard/zeromq3-x >> >> Can you see if it works Victor? >> >> -Trev >> >> >> On Wed, May 1, 2013 at 10:17 AM, Steven McCoy <[email protected]>wrote: >> >>> On 1 May 2013 08:46, Victor Perron <[email protected]> wrote: >>> >>>> call fails with err == EINVAL. >>>> In my case, this exactly happens as the last step of: >>>> - I plug my 3G dongle and connect to internet >>>> - I run my subscriber to connect to a remote publisher in the cloud ( >>>> tcp://someserver:someport ) >>>> - I unplug the 3G dongle >>>> - I wait >>>> - I plug it again : the bug happens immediately. The error code EINVAL >>>> is the same with Pieter's test case. >>>> >>>> >>> This is handled correctly in the libzmq master repo, just needs a back >>> port. A comment on catching EINVAL wouldn't go a miss either. >>> >>> -- >>> Steve-o >>> >>> _______________________________________________ >>> 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 >> >> > > > -- > Victor > -- Victor
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
