Displaying a statement history - Revision history

Ekern at 19:10, 19 April 2023

2023-04-19T19:10:28Z

← Older revision		Revision as of 19:10, 19 April 2023
Line 41:		Line 41:
	:: b. Run (mapped to a button or key, or via macro or command line) one of the Client commands that corresponds to the above mentioned menu options: [[previousHistory command\|previousHistory]], [[nextHistory command\|nextHistory]], [[firstHistory command\|firstHistory]], [[lastHistory command\|lastHistory.]]		:: b. Run (mapped to a button or key, or via macro or command line) one of the Client commands that corresponds to the above mentioned menu options: [[previousHistory command\|previousHistory]], [[nextHistory command\|nextHistory]], [[firstHistory command\|firstHistory]], [[lastHistory command\|lastHistory.]]

	: The Client responds by moving the current line to the executed statement you selected in the <var>Source Code</var> or <var>Daemon</var> page that contains the statement.		:: The Client responds by moving the current line to the executed statement you selected in the <var>Source Code</var> or <var>Daemon</var> page that contains the statement.

	: 2. Continue reviewing the executed statements by using the <var>Execution</var> menu history options or their command counterparts.		: 2. Continue reviewing the executed statements by using the <var>Execution</var> menu history options or their command counterparts.

Ekern at 19:09, 19 April 2023

2023-04-19T19:09:55Z

← Older revision		Revision as of 19:09, 19 April 2023
Line 46:		Line 46:
	:: The Client locates and highlights the statement you select, and it removes the highlighting from the statement you viewed in the previous step.		:: The Client locates and highlights the statement you select, and it removes the highlighting from the statement you viewed in the previous step.

	: '''Note:''' Although each history statement you view gets highlighted as if it were the current execution position, the actual execution position, the statement to be executed next if you invoke a debugging Step or Run operation, remains where it was when you began reviewing the statement history.		:: '''Note:''' Although each history statement you view gets highlighted as if it were the current execution position, the actual execution position, the statement to be executed next if you invoke a debugging Step or Run operation, remains where it was when you began reviewing the statement history.

	: 3. Resume normal debugging operations.		: 3. Resume normal debugging operations.

	[[Category:Debugger Home]]		[[Category:Debugger Home]]

Ekern at 19:09, 19 April 2023

2023-04-19T19:09:36Z

← Older revision		Revision as of 19:09, 19 April 2023
Line 6:		Line 6:
	: 1. In the Client's <var>Execution</var> menu, select the <var>Get/Display History</var> option.		: 1. In the Client's <var>Execution</var> menu, select the <var>Get/Display History</var> option.
	:: The <var>Execution History</var> window displays a history of statements executed up to the program's current execution point.		:: The <var>Execution History</var> window displays a history of statements executed up to the program's current execution point.
	~~<!--~~ [[File:exechist1b_zoom55.gif\|434x300px\|ExecHist1b]]~~<span class="f_ListContinue"> </span> -->~~		: [[File:exechist1b_zoom55.gif\|434x300px\|ExecHist1b]]

	:: The execution history is as many as the last 1000 statements executed. Calls and returns for methods and subroutines are labeled:		:: The execution history is as many as the last 1000 statements executed. Calls and returns for methods and subroutines are labeled:
Line 24:		Line 24:
	# Select <var>Preferences</var> from the </span><var>File</var> menu.		# Select <var>Preferences</var> from the </span><var>File</var> menu.
	# In the <var>Display Options</var> section of the <var>Preferences</var> dialog box, enable the feature by selecting the <var>History to Execution Trace</var> checkbox (it is clear by default), then click <var>Done.		# In the <var>Display Options</var> section of the <var>Preferences</var> dialog box, enable the feature by selecting the <var>History to Execution Trace</var> checkbox (it is clear by default), then click <var>Done.
	~~<!--~~ [[File:preferences23g_zoom55.gif\|556x377px\|preferences23g]]~~<span class="f_ListContinue"> </span> -->~~		: [[File:preferences23g_zoom55.gif\|556x377px\|preferences23g]]

	'''Note:''' The Client [[setPreference command\|setPreference]] command has an option that lets you toggle the <var>History to Execution Trace</var> checkbox.		'''Note:''' The Client [[setPreference command\|setPreference]] command has an option that lets you toggle the <var>History to Execution Trace</var> checkbox.

Ekern at 03:37, 4 April 2023

2023-04-04T03:37:05Z

← Older revision		Revision as of 03:37, 4 April 2023
Line 5:		Line 5:

	: 1. In the Client's <var>Execution</var> menu, select the <var>Get/Display History</var> option.		: 1. In the Client's <var>Execution</var> menu, select the <var>Get/Display History</var> option.
	:: The <var>Execution History</var> window displays a history of statements executed up to the program's current execution point:		:: The <var>Execution History</var> window displays a history of statements executed up to the program's current execution point.
			<!-- [[File:exechist1b_zoom55.gif\|434x300px\|ExecHist1b]]<span class="f_ListContinue"> </span> -->
	[[File:exechist1b_zoom55.gif\|434x300px\|ExecHist1b]]<span class="f_ListContinue"> </span>

	:: The execution history is as many as the last 1000 statements executed. Calls and returns for methods and subroutines are labeled:		:: The execution history is as many as the last 1000 statements executed. Calls and returns for methods and subroutines are labeled:
Line 25:		Line 24:
	# Select <var>Preferences</var> from the </span><var>File</var> menu.		# Select <var>Preferences</var> from the </span><var>File</var> menu.
	# In the <var>Display Options</var> section of the <var>Preferences</var> dialog box, enable the feature by selecting the <var>History to Execution Trace</var> checkbox (it is clear by default), then click <var>Done.		# In the <var>Display Options</var> section of the <var>Preferences</var> dialog box, enable the feature by selecting the <var>History to Execution Trace</var> checkbox (it is clear by default), then click <var>Done.
			<!-- [[File:preferences23g_zoom55.gif\|556x377px\|preferences23g]]<span class="f_ListContinue"> </span> -->
	[[File:preferences23g_zoom55.gif\|556x377px\|preferences23g]]<span class="f_ListContinue"> </span>

	'''Note:''' The Client [[setPreference command\|setPreference]] command has an option that lets you toggle the <var>History to Execution Trace</var> checkbox.		'''Note:''' The Client [[setPreference command\|setPreference]] command has an option that lets you toggle the <var>History to Execution Trace</var> checkbox.
Line 39:		Line 37:

	: 1. At any point during the debugging of a request after some statements have been executed, either:		: 1. At any point during the debugging of a request after some statements have been executed, either:
	:: a. Open the <var>Execution</var> menu, and click one of the history selection options: <var>[[~~execution_menu_opts.html#select_previous_history_line~~\|Select Previous History Line]]</var>, <var>[[~~execution_menu_opts.html#select_next_history_line~~\|Select Next History Line]]</var>, <var>[[~~execution_menu_opts.html#select_first_history_line~~\|Select First History Line]], </var><var>[[~~execution_menu_opts.html#select_last_history_line~~\|Select Last History Line.]]</var>		:: a. Open the <var>Execution</var> menu, and click one of the history selection options: <var>[[Execution menu options\|Select Previous History Line]]</var>, <var>[[Execution menu options\|Select Next History Line]]</var>, <var>[[Execution menu options\|Select First History Line]], </var><var>[[Execution menu options\|Select Last History Line.]]</var>
	: Or:		: Or:
	:: b. Run (mapped to a button or key, or via macro or command line) one of the Client commands that corresponds to the above mentioned menu options: [[previousHistory command\|previousHistory]], [[nextHistory command\|nextHistory]], [[firstHistory command\|firstHistory]], [[lastHistory command\|lastHistory.]]		:: b. Run (mapped to a button or key, or via macro or command line) one of the Client commands that corresponds to the above mentioned menu options: [[previousHistory command\|previousHistory]], [[nextHistory command\|nextHistory]], [[firstHistory command\|firstHistory]], [[lastHistory command\|lastHistory.]]

Ekern at 16:35, 17 October 2022

2022-10-17T16:35:10Z

Ekern: Created page with "TOC If you are in the middle of debugging a lengthy or complicated program, and you have not invoked tracing, you can produce a display of all the sta..."

2022-10-15T04:24:41Z

Created page with "__TOC__ If you are in the middle of debugging a lengthy or complicated program, and you have not invoked tracing, you can produce a display of all the sta..."

New page

__TOC__
If you are in the middle of debugging a lengthy or complicated program, and you have not invoked tracing, you can produce a display of all the statements that have already executed. Perhaps you got an unexpected runtime error or hit a breakpoint you set, and you want to review how you got to this point in the program.

To display a history of statement execution:

1. In the Client's <var>Execution</var> menu, select the <var>Get/Display History</var> option.
: The <var>Execution History</var> window displays a history of statements executed up to the program's current execution point:

[[File:exechist1b_zoom55.gif|434x300px|ExecHist1b]] 

: The execution history is as many as the last 1000 statements executed. Calls and returns for methods and subroutines are labeled:

*For a call, a (Routine/Method Call) indicator precedes the User Language statement. 
*For a return, a (Return) indicator precedes the User Language statement.
: While the <var>Execution History</var> window is open, you can interact with the main Client window, and any hot keys defined for the Client will work when the history viewer has focus.

2. Use the <var>Clear, Print</var>, <var>Save</var>, and <var>Close</var> buttons as necessary. And the search bar on the bottom of the window provides controls for searching the history.

You can also invoke this feature with the [[getHistory command|getHistory]] mappable command, clear the window with the [[clearHistory command|clearHistory]] command, and close the window with the [[closeHistory command|closeHistory]] command. 

Using the Execution Trace tab 

You can arrange to view the statement history in the <var>Execution Trace</var> page instead of in the <var>Execution History</var> window: 

1. Select <var>Preferences</var> from the <var>File</var> menu.
2. In the <var>Display Options</var> section of the <var>Preferences</var> dialog box, enable the feature by selecting the <var>History to Execution Trace</var> checkbox (it is clear by default), then click <var>Done.

[[File:preferences23g_zoom55.gif|556x377px|preferences23g]] 

'''Note:''' The Client [[setPreference command|setPreference]] command has an option that lets you toggle the <var>History to Execution Trace</var> checkbox.

3. Invoke a statement history as usual from the <var>Execution</var> menu.

=== Using the Source Code tab ===

You can review the statements in the execution history in their actual context, that is, highlighted in the program in the <var>Source Code</var> tab (or <var>Daemon</var> tab). Four <var>Execution</var> menu options (or corresponding Client commands) let you select which executed statement(s) to view: the first or the last (that is, the statement at the beginning or the end of the history), or the previous or the next executed statement, relative to the currently highlighted line. 

To inspect ''in the program code'' a previously executed statement:

1. At any point during the debugging of a request after some statements have been executed, either:
:: a. Open the <var>Execution</var> menu, and click one of the history selection options: <var>[[execution_menu_opts.html#select_previous_history_line|Select Previous History Line]]</var>, <var>[[execution_menu_opts.html#select_next_history_line|Select Next History Line]]</var>, <var>[[execution_menu_opts.html#select_first_history_line|Select First History Line]], </var><var>[[execution_menu_opts.html#select_last_history_line|Select Last History Line.]]</var>
: Or:
:: b. Run (mapped to a button or key, or via macro or command line) one of the Client commands that corresponds to the above mentioned menu options: [[previousHistory command|previousHistory]], [[nextHistory command|nextHistory]], [[firstHistory command|firstHistory]], [[lastHistory command|lastHistory.]]

: The Client responds by moving the current line to the executed statement you selected in the <var>Source Code</var> or <var>Daemon</var> page that contains the statement.

2. Continue reviewing the executed statements by using the <var>Execution</var> menu history options or their command counterparts.
: The Client locates and highlights the statement you select, and it removes the highlighting from the statement you viewed in the previous step.

'''Note:''' Although each history statement you view gets highlighted as if it were the current execution position, the actual execution position, the statement to be executed next if you invoke a debugging Step or Run operation, remains where it was when you began reviewing the statement history.

3. Resume normal debugging operations.

[[Category:Debugger Home]]

← Older revision		Revision as of 16:35, 17 October 2022
Line 1:		Line 1:
	__TOC__		__TOC__
	~~<span class="f_Para">~~If you are in the middle of debugging a lengthy or complicated program, and you have not invoked tracing, you can produce a display of all the statements that have ~~</span><span class="f_EmphItal">~~already~~</span><span class="f_Para">~~ executed. Perhaps you got an unexpected runtime error or hit a breakpoint you set, and you want to review how you got to this point in the program.~~</span>~~		If you are in the middle of debugging a lengthy or complicated program, and you have not invoked tracing, you can produce a display of all the statements that have ''already'' executed. Perhaps you got an unexpected runtime error or hit a breakpoint you set, and you want to review how you got to this point in the program.

	~~<span class="f_Para">~~To display a history of statement execution:~~</span>~~		To display a history of statement execution:

	1. In the Client's <var>Execution</var> menu, select the <var>Get/Display History</var> option.		: 1. In the Client's <var>Execution</var> menu, select the <var>Get/Display History</var> option.
	: The <var>Execution History</var> window displays a history of statements executed up to the program's current execution point:		:: The <var>Execution History</var> window displays a history of statements executed up to the program's current execution point:

	[[File:exechist1b_zoom55.gif\|434x300px\|ExecHist1b]]<span class="f_ListContinue"> </span>		[[File:exechist1b_zoom55.gif\|434x300px\|ExecHist1b]]<span class="f_ListContinue"> </span>

	: The execution history is as many as the last 1000 statements executed. Calls and returns for methods and subroutines are labeled:		:: The execution history is as many as the last 1000 statements executed. Calls and returns for methods and subroutines are labeled:

	*<span class="f_ListBul2">For a call, a </span><span class="f_Monospace">(Routine/Method Call)</span><span class="f_ListBul2"> indicator precedes the User Language statement. </span>		*<span class="f_ListBul2">For a call, a </span><span class="f_Monospace">(Routine/Method Call)</span><span class="f_ListBul2"> indicator precedes the User Language statement. </span>
Line 15:		Line 15:
	: While the </span><var>Execution History</var><span class="f_ListContinue"> window is open, you can interact with the main Client window, and any hot keys defined for the Client will work when the history viewer has focus.</span>		: While the </span><var>Execution History</var><span class="f_ListContinue"> window is open, you can interact with the main Client window, and any hot keys defined for the Client will work when the history viewer has focus.</span>

	2. Use the <var>Clear, Print</var>, </span><var>Save</var>, and </span><var>Close</var> buttons as necessary. And the search bar on the bottom of the window provides controls for searching the history.		: 2. Use the <var>Clear, Print</var>, </span><var>Save</var>, and </span><var>Close</var> buttons as necessary. And the search bar on the bottom of the window provides controls for searching the history.

	<span class="f_Para">You can also invoke this feature with the </span><span class="f_Monospace">[[getHistory command\|getHistory]]</span><span class="f_Para"> mappable command, clear the window with the </span><span class="f_Monospace">[[clearHistory command\|clearHistory]]</span><span class="f_Para"> command, and close the window with the </span><span class="f_Monospace">[[closeHistory command\|closeHistory]] </span><span class="f_Para">command. </span>		: <span class="f_Para">You can also invoke this feature with the </span><span class="f_Monospace">[[getHistory command\|getHistory]]</span><span class="f_Para"> mappable command, clear the window with the </span><span class="f_Monospace">[[clearHistory command\|clearHistory]]</span><span class="f_Para"> command, and close the window with the </span><span class="f_Monospace">[[closeHistory command\|closeHistory]] </span><span class="f_Para">command. </span>

	~~<span class~~=~~"f_Subhead">~~Using the Execution Trace ~~tab </span>~~		=== Using the Execution Trace tab ===

	~~<span class="f_Para">~~You can arrange to view the statement history in the ~~</span>~~<var>Execution Trace</var~~><span class="f_Para"~~> page instead of in ~~</span><span class="f_ListContinue">~~the ~~</span>~~<var>Execution History</var~~><span class="f_ListContinue"~~> window:~~</span><span class="f_Para"> </span>~~		You can arrange to view the statement history in the <var>Execution Trace</var> page instead of in the <var>Execution History</var> window:

	1. Select <var>Preferences</var> from the </span><var>File</var> menu.		# Select <var>Preferences</var> from the </span><var>File</var> menu.
	2. In the <var>Display Options</var> section of the <var>Preferences</var> dialog box, enable the feature by selecting the <var>History to Execution Trace</var> checkbox (it is clear by default), then click <var>Done.		# In the <var>Display Options</var> section of the <var>Preferences</var> dialog box, enable the feature by selecting the <var>History to Execution Trace</var> checkbox (it is clear by default), then click <var>Done.

	[[File:preferences23g_zoom55.gif\|556x377px\|preferences23g]]<span class="f_ListContinue"> </span>		[[File:preferences23g_zoom55.gif\|556x377px\|preferences23g]]<span class="f_ListContinue"> </span>
Line 30:		Line 30:
	'''Note:''' The Client [[setPreference command\|setPreference]] command has an option that lets you toggle the <var>History to Execution Trace</var> checkbox.		'''Note:''' The Client [[setPreference command\|setPreference]] command has an option that lets you toggle the <var>History to Execution Trace</var> checkbox.

	3. Invoke a statement history as usual from the <var>Execution</var> menu.		: 3. Invoke a statement history as usual from the <var>Execution</var> menu.

	=== Using the Source Code tab ===		=== Using the Source Code tab ===

	~~<span class="f_Para">~~You can review the statements in the execution history in their actual context, that is, highlighted in the program in the ~~</span>~~<var>Source Code</var><span class="f_Para"> tab (or </span><var>Daemon</var><span class="f_Para"> tab). Four </span><var>Execution</var~~><span class="f_ListNum1"~~> menu~~</span>~~<span class="f_Para"> options (or corresponding Client commands) let you select which executed statement(s) to view: the first or the last (that is, the statement at the beginning or the end of the history), or the previous or the next executed statement, relative to the currently highlighted line. </span>		You can review the statements in the execution history in their actual context, that is, highlighted in the program in the <var>Source Code</var><span class="f_Para"> tab (or </span><var>Daemon</var><span class="f_Para"> tab). Four </span><var>Execution</var> menu<span class="f_Para"> options (or corresponding Client commands) let you select which executed statement(s) to view: the first or the last (that is, the statement at the beginning or the end of the history), or the previous or the next executed statement, relative to the currently highlighted line. </span>

	To inspect ''in the program code'' a previously executed statement:		To inspect ''in the program code'' a previously executed statement:

	1. At any point during the debugging of a request after some statements have been executed, either:		: 1. At any point during the debugging of a request after some statements have been executed, either:
	:: a. Open the <var>Execution</var> menu, and click one of the history selection options: <var>[[execution_menu_opts.html#select_previous_history_line\|Select Previous History Line]]</var>, <var>[[execution_menu_opts.html#select_next_history_line\|Select Next History Line]]</var>, <var>[[execution_menu_opts.html#select_first_history_line\|Select First History Line]], </var><var>[[execution_menu_opts.html#select_last_history_line\|Select Last History Line.]]</var>		:: a. Open the <var>Execution</var> menu, and click one of the history selection options: <var>[[execution_menu_opts.html#select_previous_history_line\|Select Previous History Line]]</var>, <var>[[execution_menu_opts.html#select_next_history_line\|Select Next History Line]]</var>, <var>[[execution_menu_opts.html#select_first_history_line\|Select First History Line]], </var><var>[[execution_menu_opts.html#select_last_history_line\|Select Last History Line.]]</var>
	: Or:		: Or:
Line 45:		Line 45:
	: The Client responds by moving the current line to the executed statement you selected in the <var>Source Code</var> or <var>Daemon</var> page that contains the statement.		: The Client responds by moving the current line to the executed statement you selected in the <var>Source Code</var> or <var>Daemon</var> page that contains the statement.

	2. Continue reviewing the executed statements by using the <var>Execution</var> menu history options or their command counterparts.		: 2. Continue reviewing the executed statements by using the <var>Execution</var> menu history options or their command counterparts.
	: The Client locates and highlights the statement you select, and it removes the highlighting from the statement you viewed in the previous step.		:: The Client locates and highlights the statement you select, and it removes the highlighting from the statement you viewed in the previous step.

	'''Note:''' Although each history statement you view gets highlighted as if it were the current execution position, the actual execution position, the statement to be executed next if you invoke a debugging Step or Run operation, remains where it was when you began reviewing the statement history.		: '''Note:''' Although each history statement you view gets highlighted as if it were the current execution position, the actual execution position, the statement to be executed next if you invoke a debugging Step or Run operation, remains where it was when you began reviewing the statement history.

	3. Resume normal debugging operations.		: 3. Resume normal debugging operations.

	[[Category:Debugger Home]]		[[Category:Debugger Home]]

Displaying a statement history - Revision history

Ekern at 19:10, 19 April 2023

Ekern at 19:09, 19 April 2023

Ekern at 19:09, 19 April 2023

Ekern at 03:37, 4 April 2023

Ekern at 16:35, 17 October 2022

Ekern: Created page with "__TOC__ If you are in the middle of debugging a lengthy or complicated program, and you have not invoked tracing, you can produce a display of all the sta..."

Ekern: Created page with "TOC If you are in the middle of debugging a lengthy or complicated program, and you have not invoked tracing, you can produce a display of all the sta..."