Re: [zeromq-dev] Static zmq context in Windows DLL

2019-12-09 Thread Osiris Pedroso
Sorry, my previous email was sent without much time (I had an online class to attend...). The idea is to define a single instance that holds your context. When instantiating this singleton, make sure there is nothing else in the source file (the singleton instantiation is the last executable

Re: [zeromq-dev] Static zmq context in Windows DLL

2019-12-09 Thread Osiris Pedroso
In a Windows Dll, that function is named DllMain. Look for it's documentation, and there is an argument for when shutdown is happening. But it's not necessarily always called, i.e. when TerminateProcess() is called. Best bet is to define s Singleton class, define it's instance within a #pragma

Re: [zeromq-dev] Static zmq context in Windows DLL

2019-12-09 Thread Simon Giesecke
Hi, The problem will be that the destruction order is not what you expect it to be. I think overall, the least painful way to address this is to not use a global static zeromq context in your DLL, and rather pass one instance explicitly to all objects that require it. If you really don't want

[zeromq-dev] Static zmq context in Windows DLL

2019-12-09 Thread Attila Magyari
Hello, I've encountered this issue: https://github.com/zeromq/czmq/issues/1788 Basically when exiting the application, I get this error: *Assertion failed: Successful WSASTARTUP not yet performed.* I am using ZeroMQ on windows inside a DLL. I have a global static zeromq context, because I want