[zeromq-dev] the reason for zmq_assert (fetched);
Martin Hurton
hurtonm at gmail.com
Tue Aug 3 17:33:19 CEST 2010
Hi,
Can you please revert commit fd707fedc59124ed627780efed081acf33f455d2
and test again?
- Martin
On Mon, Aug 2, 2010 at 3:44 PM, hamster <YIDIEPXGXGPN at spammotel.com> wrote:
> hamster <YIDIEPXGXGPN <at> spammotel.com> writes:
>
>> It does not seem to help :( After updating from git it started to crash on
>> receive almost immidiately:
>
> The following change of zmq::xrep_t::xrecv helped to get rid off crash:
>
> =====================
> int zmq::xrep_t::xrecv (zmq_msg_t *msg_, int flags_)
> {
>
> if (prefetched) {
> zmq_msg_move (msg_, &prefetched_msg); // zmq_msg_close (msg_); inside
> more_in = msg_->flags & ZMQ_MSG_MORE;
> prefetched = false;
> return 0;
> } else {
> // Deallocate old content of the message.
> zmq_msg_close (msg_);
> }
>
> // If we are in the middle of reading a message, just grab next part of it.
> =====================
>
>
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
More information about the zeromq-dev
mailing list