I have tried to run a simple publisher in Labview and it usually crashes in the zmq_term VI, after the socket has already been closed.
Screenshot below shows the code. Everything works fine if the call to zmq_term is omitted. Is this expected behavior?
I am running Labview 11.0 (32-bit), together with a mercurial-checkout of the labview-zmq and 32-bit zmq on 64-bit Windows 7. Functionally equivalent Python code works without problems.
Any suggestions for getting more debug information? Thanks!
Thanks for your post! The crash was caused by an indexing error in the clean-up code around term(). Has been corrected and a patched version has been uploaded. I've put a lot of effort into trying to avoid LabVIEW crashing as a result of zmq's actions so am keen to squash such bugs if they pop up.
As for getting more debug info if you have problems in the future, you can recompile the DLL with the DEBUG preprocessor flag to create output in "labview-zmq.log" in the working directory (probably LabVIEW's dir).
Actually this is probably quite useful so I've added the debug DLL to the repository so you can just overwrite zmq_labview.dll with the debug version while you're developing so you can get debug output if something goes wrong.
Hope that helps.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have tried to run a simple publisher in Labview and it usually crashes in the zmq_term VI, after the socket has already been closed.
Screenshot below shows the code. Everything works fine if the call to zmq_term is omitted. Is this expected behavior?
I am running Labview 11.0 (32-bit), together with a mercurial-checkout of the labview-zmq and 32-bit zmq on 64-bit Windows 7. Functionally equivalent Python code works without problems.
Any suggestions for getting more debug information? Thanks!
Last edit: Felix Jaeckel 2012-11-01
Thanks for your post! The crash was caused by an indexing error in the clean-up code around term(). Has been corrected and a patched version has been uploaded. I've put a lot of effort into trying to avoid LabVIEW crashing as a result of zmq's actions so am keen to squash such bugs if they pop up.
As for getting more debug info if you have problems in the future, you can recompile the DLL with the DEBUG preprocessor flag to create output in "labview-zmq.log" in the working directory (probably LabVIEW's dir).
Actually this is probably quite useful so I've added the debug DLL to the repository so you can just overwrite zmq_labview.dll with the debug version while you're developing so you can get debug output if something goes wrong.
Hope that helps.