On Fri, May 20, 2011 at 6:00 PM, Martin Sustrik <[email protected]> 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. -Pieter _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
