Debugging - Revision history

Logmanoriginal: Link to actual page instead of redirect page

2023-05-06T16:48:11Z

Link to actual page instead of redirect page

← Older revision		Revision as of 16:48, 6 May 2023
Line 17:		Line 17:
	* [[Debugging Basics]]		* [[Debugging Basics]]
	* [[Execution highlighting]]		* [[Execution highlighting]]
	* [[~~Breakpoints~~]]		* [[Breakpoint]]
	* [[~~Probes~~]]		* [[Probe]]
	* [[Conditional Disable structure]]		* [[Conditional Disable structure]]
	** [[Conditional Disable structure#Symbols\|Built-in Conditional Symbols]]		** [[Conditional Disable structure#Symbols\|Built-in Conditional Symbols]]

Logmanoriginal: /* Fundamentals */ Add execution highlighting

2023-05-06T16:43:39Z

Fundamentals: Add execution highlighting

← Older revision		Revision as of 16:43, 6 May 2023
Line 16:		Line 16:
	==Fundamentals==		==Fundamentals==
	* [[Debugging Basics]]		* [[Debugging Basics]]
			* [[Execution highlighting]]
	* [[Breakpoints]]		* [[Breakpoints]]
	* [[Probes]]		* [[Probes]]

Q at 19:38, 12 March 2021

2021-03-12T19:38:01Z

← Older revision		Revision as of 19:38, 12 March 2021
Line 26:		Line 26:

	== Advanced Debugging ==		== Advanced Debugging ==
			* [[Heap Peek]]
			* [[Ned options\|Ned Options]]
	* [[Debugging_Executables\|Debugging Executables]]		* [[Debugging_Executables\|Debugging Executables]]
	\|}		\|}

	[[Category:Debugging]]		[[Category:Debugging]]

Q at 13:58, 11 March 2021

2021-03-11T13:58:54Z

← Older revision		Revision as of 13:58, 11 March 2021
Line 19:		Line 19:
	* [[Probes]]		* [[Probes]]
	* [[Conditional Disable structure]]		* [[Conditional Disable structure]]
	** [[Conditional Disable structure#Symbols\|Conditional Symbols]]		** [[Conditional Disable structure#Symbols\|Built-in Conditional Symbols]]
			** [[Conditional Disable structure#Custom conditional disable symbols\|Custom Conditional Symbols]]
	* [[Debug Window]]		* [[Debug Window]]
	* [[Error handling\|Error Handling]]		* [[Error handling\|Error Handling]]

Q at 13:51, 11 March 2021

2021-03-11T13:51:12Z

← Older revision		Revision as of 13:51, 11 March 2021
Line 3:		Line 3:
	\| '''The Debugging and Troubleshooting Portal'''		\| '''The Debugging and Troubleshooting Portal'''
	\|-		\|-
	\| '''Debugging''' is the activity of finding 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"'''''.		\| '''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"'''''.
	\|}		\|}
	__NOTOC__		__NOTOC__

Q at 13:50, 11 March 2021

2021-03-11T13:50:49Z

← Older revision		Revision as of 13:50, 11 March 2021
Line 3:		Line 3:
	\| '''The Debugging and Troubleshooting Portal'''		\| '''The Debugging and Troubleshooting Portal'''
	\|-		\|-
	\| '''Debugging''' is the activity of finding 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"''''''.		\| '''Debugging''' is the activity of finding 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"'''''.
	\|}		\|}
	__NOTOC__		__NOTOC__

Q at 13:50, 11 March 2021

2021-03-11T13:50:23Z

← Older revision		Revision as of 13:50, 11 March 2021
Line 3:		Line 3:
	\| '''The Debugging and Troubleshooting Portal'''		\| '''The Debugging and Troubleshooting Portal'''
	\|-		\|-
	\| '''Debugging''' is the activity of finding 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"''''''.		\| '''Debugging''' is the activity of finding 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"''''''.
	\|}		\|}
	__NOTOC__		__NOTOC__

Q at 13:48, 11 March 2021

2021-03-11T13:48:20Z

← Older revision		Revision as of 13:48, 11 March 2021
Line 18:		Line 18:
	* [[Breakpoints]]		* [[Breakpoints]]
	* [[Probes]]		* [[Probes]]
	* [[Conditional Disable ~~Structure~~]]		* [[Conditional Disable structure]]
	** [[Conditional Symbols]]		** [[Conditional Disable structure#Symbols\|Conditional Symbols]]
	* [[Debug Window]]		* [[Debug Window]]
	* [[Error handling\|Error Handling]]		* [[Error handling\|Error Handling]]

Q: Changed to Portal page format

2021-03-11T13:42:51Z

Changed to Portal page format

← Older revision		Revision as of 13:42, 11 March 2021
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 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/~~])		* [[Breakpoints]]
	~~</ref>~~		* [[Probes]]
			* [[Conditional Disable Structure]]
	== Conditional Disable Structure/Conditional Symbols ==		** [[Conditional Symbols]]
	~~More to come~~		* [[Debug Window]]
			* [[Error handling\|Error Handling]]
	~~== Suspend When Called ==~~		* [[Desktop Execution Trace Toolkit]]
	~~More to come~~

	== Debug Window ==
	~~More to come~~

	== Error Handling ==
	~~More to come~~

	== Desktop Execution Trace Toolkit ==
	~~More to come~~

	== Advanced Debugging ==		== Advanced Debugging ==
	* [[Debugging_Executables\|Debugging Executables]]		* [[Debugging_Executables\|Debugging Executables]]
	~~More to come~~		\|}

	~~== Tips and tricks ==~~
	* Use conditional probes to break code execution when a specified condition is met.
	* To edit a VI that is set to run when opened, open the VI from the block diagram of another VI.
	* Select '''Edit > Remove Breakpoints from Hierarchy''' to quickly remove all breakpoints in the hierarchy.
	* A call list will appear in the toolbar on the block diagram of a subVI while it is paused or suspended. This list contains all the callers the VI. Choose an entry to highlight the subVI in the caller.

	~~== External links ==~~
	~~[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]]

Logmanoriginal: Add tips and tricks

2020-05-15T12:11:30Z

Add tips and tricks

← Older revision		Revision as of 12:11, 15 May 2020
Line 38:		Line 38:
	More to come		More to come

	== ~~Articles~~ ==		== Tips and tricks ==
			* Use conditional probes to break code execution when a specified condition is met.
			* To edit a VI that is set to run when opened, open the VI from the block diagram of another VI.
			* Select '''Edit > Remove Breakpoints from Hierarchy''' to quickly remove all breakpoints in the hierarchy.
			* A call list will appear in the toolbar on the block diagram of a subVI while it is paused or suspended. This list contains all the callers the VI. Choose an entry to highlight the subVI in the caller.

			== External links ==
	[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		[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