[zeromq-dev] Valgrind warnings

Steven McCoy steven.mccoy at miru.hk
Mon Jun 13 21:16:40 CEST 2011

On 13 June 2011 15:09, Oliver Smith <oliver at kfs.org> wrote:

>  After adding ZeroMQ for tcp communication between some processes to help
> coordinate a test run, I started getting valgrind warnings as follows;
> unfortunately I haven't got time just now to look deeper...
>  ==12019== Syscall param socketcall.send(msg) points to uninitialised byte(s)
> ==12019==    at 0x4243A78: send (socket.S:100)
> ==12019==    by 0x40DE4CC: zmq::ctx_t::send_command(unsigned int, zmq::command_t const&) (in /playnet/wwiiol/lib/libzmq.so.1.0.0

Same affected command structure as before, I think it used to be in the FAQ,


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20110613/d43c8fd2/attachment.htm>

More information about the zeromq-dev mailing list