[zeromq-dev] [PATCH] Improved response to socket violations

Marko Mikulicic marko.mikulicic at isti.cnr.it
Fri May 20 18:22:36 CEST 2011

On 20 May 2011 18:09, Pieter Hintjens <ph at imatix.com> wrote:

> On Fri, May 20, 2011 at 6:00 PM, Martin Sustrik <sustrik at 250bpm.com>
> wrote:
> > The problem is that using single socket from mutliple threads can cause
> > basically any error, whether assertion, segfault or whatever. Singling
> > this one out doesn't make much sense. Moreover, as Mato points out, the
> > assertion can happen because of limited OS resources, in which case the
> > message would be misleading.
> So the repeated instances of this particular assertion failure are
> just coincidence?
> Fair enough, but it reflects badly on 0MQ that it can't more
> accurately detect and report such a common application error.

What if the library could be compiled or parameterized with a "debug"
flag/envvar, which enables thread identity checks and issue a warning
if a socket is being used by two different threads at runtime? Then there
will be a canned response for everybody reporting issues (please enabled
debugging and try again),
and still have a fast default path.

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

More information about the zeromq-dev mailing list