Tools Debugger/en - Versionsgeschichte

Cg: /* Entering the Debugger via the Interrupt Key */

2022-03-14T11:00:48Z

Entering the Debugger via the Interrupt Key

← Nächstältere Version		Version vom 14. März 2022, 11:00 Uhr
Zeile 64:		Zeile 64:
	Although we take good care to avoid/find/and fix such situations, and they are really very very rare, you can still interrupt the system with the interrupt key, which is <kbd>CTRL-.</kbd>, <kbd>CMD-.</kbd> or <kbd>INTR/PAUSE</kbd>, depending on your operating system and keyboard layout. This interrupts the current activity and opens a debugger on the activity. The "''Test Run''" tab also includes an interrupt toolbar button for this at the top right side.		Although we take good care to avoid/find/and fix such situations, and they are really very very rare, you can still interrupt the system with the interrupt key, which is <kbd>CTRL-.</kbd>, <kbd>CMD-.</kbd> or <kbd>INTR/PAUSE</kbd>, depending on your operating system and keyboard layout. This interrupts the current activity and opens a debugger on the activity. The "''Test Run''" tab also includes an interrupt toolbar button for this at the top right side.

	Depending on the operating system used (Linux vs. MS Windows vs. Mac-OSX), some operations cannot be interrupted. For example, on Windows, some of the API calls are uninterruptable.		Depending on the operating system used (Linux vs. MS Windows vs. Mac-OSX), some operations cannot be interrupted. For example, on Windows, some of the system API calls are uninterruptable.

	Back to [[Online_Documentation#Tools \| Online Documentation]].		Back to [[Online_Documentation#Tools \| Online Documentation]].

Cg: /* Entering the Debugger via the Interrupt Key */

2022-03-14T11:00:27Z

Entering the Debugger via the Interrupt Key

← Nächstältere Version		Version vom 14. März 2022, 11:00 Uhr
Zeile 64:		Zeile 64:
	Although we take good care to avoid/find/and fix such situations, and they are really very very rare, you can still interrupt the system with the interrupt key, which is <kbd>CTRL-.</kbd>, <kbd>CMD-.</kbd> or <kbd>INTR/PAUSE</kbd>, depending on your operating system and keyboard layout. This interrupts the current activity and opens a debugger on the activity. The "''Test Run''" tab also includes an interrupt toolbar button for this at the top right side.		Although we take good care to avoid/find/and fix such situations, and they are really very very rare, you can still interrupt the system with the interrupt key, which is <kbd>CTRL-.</kbd>, <kbd>CMD-.</kbd> or <kbd>INTR/PAUSE</kbd>, depending on your operating system and keyboard layout. This interrupts the current activity and opens a debugger on the activity. The "''Test Run''" tab also includes an interrupt toolbar button for this at the top right side.

	Depending on the operating system used (Linux vs. MS Windows vs. Mac-OSX), some operations cannot be interrupted. For example, on Windows, some ~~OS-~~API calls are uninterruptable.		Depending on the operating system used (Linux vs. MS Windows vs. Mac-OSX), some operations cannot be interrupted. For example, on Windows, some of the API calls are uninterruptable.

	Back to [[Online_Documentation#Tools \| Online Documentation]].		Back to [[Online_Documentation#Tools \| Online Documentation]].

Cg: /* Things You Cannot Change */

2022-03-14T10:59:28Z

Things You Cannot Change

← Nächstältere Version		Version vom 14. März 2022, 10:59 Uhr
Zeile 55:		Zeile 55:
	=== Things You Cannot Change ===		=== Things You Cannot Change ===

	Expecco protects itself from modifications done to itself. So you cannot modify code of the expecco application. Actually, since only the source code of the basic framework ~~classes, but not the expecco application~~ classes is deployed, you will not even be able to see the internals of the expecco system.		Expecco protects itself from modifications done to itself. So you cannot modify code of the expecco application. Actually, since only the source code of the basic framework classes is deployed, you will not even be able to see the internals of the expecco system.

	This is not a bug but done by purpose.		This is not a bug but done by purpose.

Cg: /* What is Shown by the Debugger */

2022-03-14T10:58:10Z

What is Shown by the Debugger

← Nächstältere Version		Version vom 14. März 2022, 10:58 Uhr
Zeile 34:		Zeile 34:
	== What is Shown by the Debugger ==		== What is Shown by the Debugger ==

	The debugger displays the state of the suspended program in multiple panes. The top pane shows a walkback (also named "''call chain''"), presenting the calling functions. Click to select one of the callers to see how and where it called the function in error.		The debugger displays the state of the suspended program in multiple panes. The top pane shows a walkback (also named "''call chain''"), presenting the calling functions, callers below the called function. Click to select one of the callers to see how and where it called the function in error.

	When selected, the function's source code and current execution line number is shown in the middle pane.		When selected, the function's source code and current execution line number is shown in the middle pane.

	Notice, that you should have checked the "''Install Source Code''" toggle in the initial installation; otherwise, the debugger will not be able to show the source code. If you did not, please repeat the installation process, checking the "''Install Source Code''" toggle.		Notice, that you should have checked the "''Install Source Code''" toggle in the initial installation; otherwise, the debugger will not be able to show the source code. If you did not, please repeat the installation process, checking the "''Install Source Code''" toggle.
	Also notice, that not all of expecco's code is deployed and published. Only the parts of the underlying open source Smalltalk/X code can be seen (which can also be downloaded from the Smalltalk/X web site, or accessed via the CVS repository).		<br>Also notice, that not all of expecco's source code is deployed and published. Only the parts of the underlying open source Smalltalk/X code can be seen (which can also be downloaded from the Smalltalk/X web site, or accessed via the CVS repository).

	The lower pane displays the contents of the receiving object (i.e. the object of which a function was called) on the left, and call-arguments plus local variables of the function on the right.		The lower pane displays the contents of the receiving object (i.e. the object of which a function was called) on the left, and call-arguments plus local variables of the function on the right.
	These are standard inspector windows, so they allow code evaluation ("''doIt''") and following references by double click on a selected item.		<br>These are standard inspector windows, so they allow code evaluation ("''doIt''") and following references by double click on a selected item.

	== Programming in the Debugger ==		== Programming in the Debugger ==

Cg: /* Aborting vs. Terminating vs. Proceeding */

2022-03-14T09:28:16Z

Aborting vs. Terminating vs. Proceeding

← Nächstältere Version		Version vom 14. März 2022, 09:28 Uhr
Zeile 19:		Zeile 19:
	If you are not interested in further investigation of the error, simply press the "''Abort''" button to finish the current activity (with an Error-verdict).		If you are not interested in further investigation of the error, simply press the "''Abort''" button to finish the current activity (with an Error-verdict).

	Avoid the "''Terminate''" button, as this will kill the underlying thread. This should be only used as a last chance, when an error is reported again and again. Often termination will close the underlying thread's window, which may be the expecco-window. Always first try to "''Abort''" a few times before terminating.		Avoid the red "''Terminate''" button, as this will kill the underlying thread. This should be only used as a last chance, when an error is reported again and again. Often termination will close the underlying thread's window, which may be the expecco-window. Always first try to "''Abort''" a few times before terminating.

	Some errors are proceedable, if they are considered to be non-severe. For example a "''File-Not-Found''" error might be proceedable and the program would then continue with a <code>nil</code> file handle (which may of course lead to future errors, if the nil-handle is ever used for I/O operations). The proceedability depends on the way the error was signalled and is usually a choice of the programmer (i.e. whether the code which uses a file is prepared to deal with a <code>nil</code> handle).		Some errors are proceedable, if they are considered to be non-severe. For example a "''File-Not-Found''" error might be proceedable and the program would then continue with a <code>nil</code> file handle (which may of course lead to future errors, if the nil-handle is ever used for I/O operations). The proceedability depends on the way the error was signalled and is usually a choice of the programmer (i.e. whether the code which uses a file is prepared to deal with a <code>nil</code> handle).

Cg: /* Introduction */

2022-03-14T09:27:10Z

Introduction

← Nächstältere Version		Version vom 14. März 2022, 09:27 Uhr
Zeile 1:		Zeile 1:
	== Introduction ==		== Introduction ==
	The Debugger is opened whenever an error or a halt/breakpoint is encountered while a Smalltalk or JavaScript elementary block's code is executed, and you have either enabled the "''Open Debugger on...''" ~~option~~ in the settings or started a block-test run via the "''Run-and-Debug''" button.		The Debugger is opened whenever an error or a halt/breakpoint is encountered while a Smalltalk or JavaScript elementary block's code is executed, and you have either enabled one of the "''Open Debugger On...''" options in the settings or started a block-test run via the "''Run-and-Debug''" button (the red "play" button).

	A variant of the debugger is opened if an error or breakpoint is encountered in a bridged Node.JS action.		A variant of the debugger is opened if an error or breakpoint is encountered in a bridged Node.JS or bridged Python action.

	Currently the debugger cannot be used with Groovy and with code which is executed on a remote machine or in an external JVM.		Currently the debugger cannot be used with Groovy and with code which is executed on a remote machine or in an external JVM.

	If the debug options are disabled in the settings, no debugger will be shown, and the ~~elementary~~ action is finished with an Error-verdict.		If the debug options are disabled in the settings, no debugger will be shown, and the action is finished with an Error-verdict.

	Typical situations in which the debugger pops up are Division-by-Zero, Index-Bounds-Errors, File-Not-Found-Errors etc.		Typical situations in which the debugger pops up are Division-by-Zero, Index-Bounds-Errors, File-Not-Found-Errors etc.
	However, the debugger is also opened if you put a breakpoint (or a programmed halt~~-call~~) into your elementary block's code.		However, the debugger is also opened if you put a breakpoint (or a programmed halt) into your elementary block's code.

	The debugger's [http://live.exept.de/doc/online/english/tools/debugger/TOP.html full documentation] is part of the official [http://live.exept.de/doc/online/english/TOP.html Smalltalk/X Online Documentation].		The debugger's [http://live.exept.de/doc/online/english/tools/debugger/TOP.html full documentation] is part of the official [http://live.exept.de/doc/online/english/TOP.html Smalltalk/X Online Documentation].

Cg: /* Introduction */

2019-03-16T10:45:14Z

Introduction

← Nächstältere Version		Version vom 16. März 2019, 10:45 Uhr
Zeile 11:		Zeile 11:
	However, the debugger is also opened if you put a breakpoint (or a programmed halt-call) into your elementary block's code.		However, the debugger is also opened if you put a breakpoint (or a programmed halt-call) into your elementary block's code.

	The ~~tool~~'s [http://live.exept.de/doc/online/english/tools/debugger/TOP.html full documentation] is part of the official [http://live.exept.de/doc/online/english/TOP.html Smalltalk/X Online Documentation].		The debugger's [http://live.exept.de/doc/online/english/tools/debugger/TOP.html full documentation] is part of the official [http://live.exept.de/doc/online/english/TOP.html Smalltalk/X Online Documentation].

	This is an expert tool, useful to coders only.		This is an expert tool, useful to coders only.

Cg: /* Entering the Debugger via the Interrupt Key */

2019-03-16T10:44:26Z

Entering the Debugger via the Interrupt Key

← Nächstältere Version		Version vom 16. März 2019, 10:44 Uhr
Zeile 64:		Zeile 64:
	Although we take good care to avoid/find/and fix such situations, and they are really very very rare, you can still interrupt the system with the interrupt key, which is <kbd>CTRL-.</kbd>, <kbd>CMD-.</kbd> or <kbd>INTR/PAUSE</kbd>, depending on your operating system and keyboard layout. This interrupts the current activity and opens a debugger on the activity. The "''Test Run''" tab also includes an interrupt toolbar button for this at the top right side.		Although we take good care to avoid/find/and fix such situations, and they are really very very rare, you can still interrupt the system with the interrupt key, which is <kbd>CTRL-.</kbd>, <kbd>CMD-.</kbd> or <kbd>INTR/PAUSE</kbd>, depending on your operating system and keyboard layout. This interrupts the current activity and opens a debugger on the activity. The "''Test Run''" tab also includes an interrupt toolbar button for this at the top right side.

	Depending on the operating system used (Linux vs. MS Windows vs. Mac-OSX), some operations cannot be interrupted. For example, on MS Windows, some OS-API calls are uninterruptable.		Depending on the operating system used (Linux vs. MS Windows vs. Mac-OSX), some operations cannot be interrupted. For example, on Windows, some OS-API calls are uninterruptable.

	Back to [[Online_Documentation#Tools \| Online Documentation]].		Back to [[Online_Documentation#Tools \| Online Documentation]].

Cg: /* Entering the Debugger via the Interrupt Key */

2019-03-16T10:44:05Z

Entering the Debugger via the Interrupt Key

← Nächstältere Version		Version vom 16. März 2019, 10:44 Uhr
Zeile 64:		Zeile 64:
	Although we take good care to avoid/find/and fix such situations, and they are really very very rare, you can still interrupt the system with the interrupt key, which is <kbd>CTRL-.</kbd>, <kbd>CMD-.</kbd> or <kbd>INTR/PAUSE</kbd>, depending on your operating system and keyboard layout. This interrupts the current activity and opens a debugger on the activity. The "''Test Run''" tab also includes an interrupt toolbar button for this at the top right side.		Although we take good care to avoid/find/and fix such situations, and they are really very very rare, you can still interrupt the system with the interrupt key, which is <kbd>CTRL-.</kbd>, <kbd>CMD-.</kbd> or <kbd>INTR/PAUSE</kbd>, depending on your operating system and keyboard layout. This interrupts the current activity and opens a debugger on the activity. The "''Test Run''" tab also includes an interrupt toolbar button for this at the top right side.

	Depending on the operating system used (Linux vs. MS Windows vs. ~~macOS~~), some operations cannot be interrupted. For example, on MS Windows, some OS-API calls are uninterruptable.		Depending on the operating system used (Linux vs. MS Windows vs. Mac-OSX), some operations cannot be interrupted. For example, on MS Windows, some OS-API calls are uninterruptable.

	Back to [[Online_Documentation#Tools \| Online Documentation]].		Back to [[Online_Documentation#Tools \| Online Documentation]].

Cg: /* Entering the Debugger via the Interrupt Key */

2019-03-16T10:43:13Z

Entering the Debugger via the Interrupt Key

← Nächstältere Version		Version vom 16. März 2019, 10:43 Uhr
Zeile 62:		Zeile 62:

	If the system seems to no longer react (or is executing an endless loop), you should normally be able to stop/pause the execution via the execution control buttons. In very rare situations, these may seem to not react, and the systems seems frozen. This happens if a system lock (semaphore) is kept and not freed, or if a high priority process executes an endless loop.		If the system seems to no longer react (or is executing an endless loop), you should normally be able to stop/pause the execution via the execution control buttons. In very rare situations, these may seem to not react, and the systems seems frozen. This happens if a system lock (semaphore) is kept and not freed, or if a high priority process executes an endless loop.
	Although we take good care to avoid/find/and fix such situations, and they are really very very rare, you can still interrupt the system with the interrupt key (<kbd>CTRL-.</kbd>, <kbd>CMD-.</kbd> or <kbd>INTR/PAUSE</kbd>, depending on your operating system and keyboard layout) ~~and~~ ~~force a debugger to be opened and~~ the current activity to be ~~suspended~~ or ~~aborted~~. The "''Test Run''" tab also includes an interrupt toolbar button for this at the top right side.		Although we take good care to avoid/find/and fix such situations, and they are really very very rare, you can still interrupt the system with the interrupt key, which is <kbd>CTRL-.</kbd>, <kbd>CMD-.</kbd> or <kbd>INTR/PAUSE</kbd>, depending on your operating system and keyboard layout. This interrupts the current activity and opens a debugger on the activity. The "''Test Run''" tab also includes an interrupt toolbar button for this at the top right side.

	Depending on the operating system used (Linux vs. MS Windows vs. macOS), some operations cannot be interrupted. For example, on MS Windows, some OS-API calls are uninterruptable.		Depending on the operating system used (Linux vs. MS Windows vs. macOS), some operations cannot be interrupted. For example, on MS Windows, some OS-API calls are uninterruptable.