[zeromq-dev] frequent ZeroMQ crashes - how to diagnose?

Martin Sustrik sustrik at 250bpm.com
Fri Jul 9 10:10:33 CEST 2010


Nick,

> ZeroMQ Assert Fail details
> 
> To diagnose, I captured the value of WSAGetLastError () before the assert failed. The value is 10014. After looking it up, this appears to be WSAEFAULT (Bad address) 
> Up to the point the assert failed, my application sent out approximately 6,000 messages on this socket (approximately 15 minutes) successfully. The socket transport type is tcp, and address/port is 192.168.1.7:1234 (local network)
> 
> from http://msdn.microsoft.com/en-us/library/ms740668%28VS.85%29.aspx
> WSAEFAULT 10014 
> Bad address. The system detected an invalid pointer address in attempting to use a pointer argument of a call. This error occurs if an application passes an invalid pointer value, or if the length of the buffer is too small. For instance, if the length of an argument, which is a sockaddr structure, is smaller than the sizeof(sockaddr).
> 
> Is it possible to fix this by simply adding WSAEFAULT to the error trapping list below?

No. It won't help.

Unallocated memory is used. This can be either bug in 0MQ or incorrect 
handling of zmq_msg_t in the client application. Do you have a test 
program to reproduce the problem?

Martin



More information about the zeromq-dev mailing list