[zeromq-dev] Valgrind mutters about uninitialized values

Martin Sustrik sustrik at 250bpm.com
Tue Mar 1 08:38:55 CET 2011

Hi Andreas,

> I'm using a request/reply setting which seems to
> be working quite fine. But Valgrind keeps spamming
> a lot of the following error messages:
> ==9551== Syscall param socketcall.sendto(msg) points to uninitialised
> byte(s)
> (Appears in the application and the ZeroMQ thread)
> What is happening here?

Some bytes that are not used are not being nullified (for performance 

If you want valgrind to shut up, compile 0MQ with 


More information about the zeromq-dev mailing list