Whenever I compile and run the debuggable executable labwindows will suspend execution after running for a short period of time. The wierd part is that this only happens on certain computers and when it suspends execution it goes to the same part of my code evertime. It does not give me any errors or user dialogues. After I press 'GO' twice my program goes back to where it left off with no problems.
Some windows SDK functions send breakpoint exceptions when called with invalid parameters. For example, the underlying Windows SDK function used in CA_FreeMemory suspends execution when debugging an executable if you're trying to free memory not allocated by the automation server, or if you've already freed the memory. This only happens (AFAIK) on WinNT/2000 but not on Win98/ME.