|
|
| (9 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| == Debugging Basics == | | {| class="wikitable" style="width:100%;" |
| [[File:BD Toolbar.gif|center|thumb|506x506px|Block Diagram Toolbar ]]
| | |- style="background-color:#616366; font-size:200%; border:none; margin:0; padding:.3em; color:#FFD500; text-align:center;" |
| Basic debugging tools come integrated into every block diagram window in the toolbar. See [http://www.ni.com/getting-started/labview-basics/debug Debugging Tools in LabVIEW] .<ref>"Debugging Tools in LabVIEW" by National Instruments ([http://www.ni.com/getting-started/labview-basics/debug]http://www.ni.com/getting-started/labview-basics/debug)
| | | '''The Debugging and Troubleshooting Portal''' |
| </ref>
| | |- |
| * '''Broken Run Button''' - appears broken when the VI you are creating or editing contains errors
| | | '''Debugging''' is the activity of finding and removing discrepancies in the source code that cause the code either to not compile (see [[Broken Run button]]), to not execute, to execute with errors, or to execute in an unexpected or undesirable way; all of which are refered to as '''''"Bugs"'''''. |
| * '''Highlight Execution''' - displays an animation of the block diagram execution when you run the VI
| | |} |
| * '''Retain Wire Values''' - save the wire values at each point in the flow of execution so that when you place a probe on the wire you can immediately retain the most recent value of the data that passed through the wire
| | __NOTOC__ |
| * '''Step Into''' - opens a node and pauses
| | {| class="wikitable" style="width:100%;" |
| * '''Step Over''' - executes a node and pauses at the next node
| | |- style="background-color:#616366; border:none; color:#FFD500; text-align:center;" |
| * '''Step Out''' - finishes executing the current node and pauses
| | | '''Subcategories''' |
| | | | colspan=3 | '''Topics in Debugging and Troubleshooting''' |
| == Breakpoints == | | |- style="vertical-align:top;" |
| [[File:BreakpointButton.gif|left|frameless|24x24px]]
| | | style="width:25%; text-align:top; background-color:#EFEFEF;" | <center><small>Select [►] to view subcategories</small></center> |
| Like other software languages, breakpoints allow the developer to pause the execution of the code at a specified point. This is helpful when the developer knows the code works to that point but the wants to use the other debugging to past that point to discover the problem. See more on [https://zone.ni.com/reference/en-XX/help/371361J-01/lvhowto/breakpoints/ Managing Breakpoints].<ref>"Managing Breakpoints" by National Instruments (http://zone.ni.com/reference/en-XX/help/371361R-01/lvhowto/breakpoints/)</ref>
| | <categorytree mode="Pages" showcount="off" depth="1">Debugging</categorytree> |
| | | | style="width:75%;" | |
| == Probes == | | ==Fundamentals== |
| [[File:ProbeButton.gif|left|frameless|24x24px]] | | * [[Debugging Basics]] |
| Use [[Probes]] to check intermediate values on a wire as a VI runs. Use the Probe tool if you have a complicated block diagram with a series of operations, any one of which might return incorrect data. Use the Probe tool with execution highlighting, single-stepping, and breakpoints to determine if and where data is incorrect. If data is available, the probe immediately updates and displays the data during execution highlighting, single-stepping, or when you pause at a breakpoint. When execution pauses at a node because of single-stepping or a breakpoint, you also can probe the wire that just executed to see the value that flowed through that wire.<ref>"Using the Probe Tool" by National Instruments [http://zone.ni.com/reference/en-XX/help/371361R-01/lvhowto/using_the_probe_tool/ (http://zone.ni.com/reference/en-XX/help/371361R-01/lvhowto/using_the_probe_tool/])
| | * [[Execution highlighting]] |
| </ref>
| | * [[Breakpoint]] |
| | | * [[Probe]] |
| == Conditional Disable Structure/Conditional Symbols ==
| | * [[Conditional Disable structure]] |
| More to come
| | ** [[Conditional Disable structure#Symbols|Built-in Conditional Symbols]] |
| | | ** [[Conditional Disable structure#Custom conditional disable symbols|Custom Conditional Symbols]] |
| == Suspend When Called ==
| | * [[Debug Window]] |
| More to come
| | * [[Error handling|Error Handling]] |
| | | * [[Desktop Execution Trace Toolkit]] |
| == Debug Window ==
| |
| More to come
| |
| | |
| == Error Handling ==
| |
| More to come
| |
| | |
| == Desktop Execution Trace Toolkit ==
| |
| More to come
| |
|
| |
|
| == Advanced Debugging == | | == Advanced Debugging == |
| | * [[Heap Peek]] |
| | * [[Ned options|Ned Options]] |
| * [[Debugging_Executables|Debugging Executables]] | | * [[Debugging_Executables|Debugging Executables]] |
| More to come
| | |} |
| | |
| == Articles ==
| |
| [https://forums.ni.com/t5/WAsatch-Front-LabVIEW-WAFL-User/Basics-of-Debugging-LabVIEW/gpm-p/3816405 Basics of Debugging LabVIEW] - by Quentin Alldredge, Q Software Innovations, LLC
| |
| | |
| == References ==
| |
| <references />
| |
|
| |
|
| [[Category:Debugging]] | | [[Category:Debugging]] |
