[zeromq-dev] Improper socket/context shutdown and some other questions
Rabedik
rabedik at gmail.com
Fri Feb 24 23:48:17 CET 2012
That makes sense I suppose, although why would the internal signalling
object report that it hadn't been started? Would that indicate that I was
accidentally trying to shut down the context after already shutting it down
once?
Thanks
On Thu, Feb 23, 2012 at 2:05 PM, john skaller <skaller at users.sourceforge.net
> wrote:
>
> On 24/02/2012, at 8:49 AM, Rabedik wrote:
> >
> > Assertion failed: Successful WSASTARTUP not yet performed
> (..\..\..\src\signaler.cpp:124)
> >
> > This doesn't make sense to me because data was flowing through the
> socket, so the socket would have to be started.
>
> I think .. I'm no Windows expert .. that WSA is not the sockets .. its the
> signalling object
> used for event management. WS = WaitForSingle.
>
> --
> john skaller
> skaller at users.sourceforge.net
> http://felix-lang.org
>
>
>
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20120224/8c02d486/attachment.htm>
More information about the zeromq-dev
mailing list