Download LabWindows/CVI User Manual

Source, Interactive Execution, and Standard Input/Output Windows
Chapter 4
LabWindows/CVI terminates, closes, or deletes these program elements only when one of the
following events occurs:
•
You select Clear Interactive Declarations from the Build menu.
•
You link a project.
•
You run a project.
Run-time Error Reporting
LabWindows/CVI reports various run-time errors during the execution of a program. For
instance, a call to a LabWindows/CVI library function with an array or string too small to hold
the output data is one example of a run-time error.
When such errors occur, a dialog box appears identifying the type of error and the location in the
file where the error occurred. LabWindows/CVI then displays the error in the Runtime Error
window.
LabWindows/CVI suspends the program so you can inspect the values of variables in the
Variable Display window. To terminate a program that has been suspended because of a runtime error, select the Terminate Execution command or <Ctrl-Alt-SysRq> under Windows 3.1
or <Ctrl-F12> under Windows 95, Windows NT, and UNIX.
Continue
Use the Continue command to resume program execution when in a breakpoint state.
Go to Cursor
When the program is in a breakpoint state, you can move the keyboard cursor to a line in the
program and select Go to Cursor. Program execution then continues until it reaches that line,
where it will enter another breakpoint state.
Step Over
Use Step Over to execute an outlined statement while in a breakpoint state. If the program is
breakpointed on a function call statement, Step Over executes the entire function and then
breakpoints on the statement following the function call. If a breakpoint is encountered within
the function call, Step Over pauses at the breakpoint.
LabWindows/CVI User Manual
4-28
© National Instruments Corporation