When I ran into this issue in my code, it was flooding a device with messages that most reliably caused the issue to arise. The problem seems to be that the free is an asynchronous event, so I think you aren't guaranteed that the free will happen before the second send. The second send has to take long enough to initiate that the free has taken place.
-MinRK On Tue, Sep 28, 2010 at 08:36, Pieter Hintjens <[email protected]> wrote: > I'm sorry, Martin, trying to make a reproducible case and the problem > doesn't happen. It must have been confusion on my part... but this is > good, I can now document zmq_msg_copy properly in the guide. > > Thanks > Pieter > > On Tue, Sep 28, 2010 at 5:27 PM, Pieter Hintjens <[email protected]> wrote: > > OK. > > > > On Tue, Sep 28, 2010 at 1:43 PM, Martin Sustrik <[email protected]> > wrote: > >> On 09/28/2010 01:38 PM, Pieter Hintjens wrote: > >>> > >>> Except it does not work, when you send m1 m2 is also cleared. > >> > >> :( > >> > >> Report it as a bug please. > >> > >> Thanks. > >> Martin > >> > >> > > > > > > > > -- > > - > > Pieter Hintjens > > iMatix - www.imatix.com > > > > > > -- > - > Pieter Hintjens > iMatix - www.imatix.com > _______________________________________________ > 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
