Though you can certainly change the implementation of the
example as you see fit! One possible way
to debug this situation is to create a log file which will trace all the calls
to the breakonlibraryerrors functions.
You could create a single file “programtrace.txt” and just write a line “enable\n”
or “disable\n” to the file for each corresponding call. Whenever you get a library error unexpectedly
you could open the file. If the last
entry in the file is “disable” then there is clearly something wrong happening
or another execution thread that you have not written is enabling the
errors. If the last call in the file is “enable”,
the problem lies somewhere in your code which results in the library errors
being enabled. Hopefully this will shed a little more light
on the situation.
Travis M
LabVIEW R&D
National Instruments
