Ide/Debugger - Revision history

Thomas Linder Puls: /* Debug Adapter */ Released

2024-01-11T12:01:58Z

Debug Adapter: Released

← Older revision		Revision as of 14:01, 11 January 2024
Line 9:		Line 9:

	== Debug Adapter ==		== Debug Adapter ==

	~~{{Template:NonReleased}}~~

	Starting from version 11, Visual Prolog employs a Debug Adapter for the debugging process.		Starting from version 11, Visual Prolog employs a Debug Adapter for the debugging process.

Thomas Linder Puls at 10:19, 21 December 2023

2023-12-21T10:19:24Z

← Older revision		Revision as of 12:19, 21 December 2023
Line 2:		Line 2:
	== Visual Prolog Debugger ==		== Visual Prolog Debugger ==

	Visual Prolog ~~Debugger~~ is a powerful tool for finding errors in programs. ~~Sometimes correcting errors in programs takes about 90% of the total development time. This proves that good tools for debugging are very important~~.		Visual Prolog debugger is a powerful tool for finding errors in programs. It can debug MS Windows 32/64-bit Graphical User Interface and Console applications and DLLs.

	~~Visual~~ Prolog ~~Debugger can debug MS Windows 32/64-bit Graphical User Interface~~ and ~~Console applications~~ and ~~DLLs~~.		The debugger provides ability to trace program execution. Within the debugger, users can establish breakpoints, navigate through the source code (with code tracing available on both Prolog and disassembler levels), inspect variables within the presently traced clause, view facts, analyze memory dumps, observe the stack of predicate calls, explore inserted breakpoints, review registers, and more.

	Visual Prolog Debugger provides ability to trace program execution. In the debugger one can set breakpoints, step through the source code (with viewing traced code both on Prolog and disassembler levels). The debugger allows inspecting variables used in the currently traced clause, viewing and retracting facts, viewing memory dumps, viewing the stack of predicate calls, viewing breakpoints inserted into the program, viewing registers, etc.		To start debugging use the '''Debug \| Run''' menu command, the '''F5''' hot key, or the [Image:Ide_db_Run.png]] toolbar button.

	~~Visual Prolog Debugger is the IDE tool, which can be run with~~ the '''Debug \| Run''' menu command, ~~with~~ the '''F5''' hot key, or ~~with~~ the [[Image:Ide_db_Run.png]] toolbar button.

	== Debug Adapter ==		== Debug Adapter ==

Thomas Linder Puls: Review

2023-12-21T09:48:23Z

Review

← Older revision		Revision as of 11:48, 21 December 2023
Line 14:		Line 14:
	{{Template:NonReleased}}		{{Template:NonReleased}}

	~~Since~~ version 11 Visual Prolog ~~uses~~ a ~~'''~~Debug Adapter~~'''~~ for the debugging process.		Starting from version 11, Visual Prolog employs a Debug Adapter for the debugging process.

	A Debug Adapter is ~~an independent~~ program that ~~connects to~~ the debugged process. Instead of attaching ~~directly~~ to the debugged process, the IDE ~~launches establishes~~ communication with ~~this~~ Debug Adapter. This approach offers a practical advantage: it ~~allows~~ a 64-bit IDE to ~~communicate~~ with a 32-bit Debug Adapter, ~~enabling~~ the debugging of 32-bit processes ~~alongside~~ 64-bit programs.		A Debug Adapter is a standalone program that establishes a connection with the debugged process. Instead of directly attaching to the debugged process, the Integrated Development Environment (IDE) initiates communication with the Debug Adapter upon launch. This approach offers a practical advantage: it enables a 64-bit IDE to interact with a 32-bit Debug Adapter, facilitating the debugging of both 32-bit processes and 64-bit programs.

	~~As a consequence~~ in Visual Prolog 11 the IDE is ~~always~~ a 64-bit program.		Consequently, in Visual Prolog 11, the IDE is exclusively a 64-bit program.

	The communication between the IDE and the Debug Adapter adheres to the [https://microsoft.github.io/debug-adapter-protocol/ Debug Adapter Protocol] standard.		The communication between the IDE and the Debug Adapter adheres to the [https://microsoft.github.io/debug-adapter-protocol/ Debug Adapter Protocol] standard.

Thomas Linder Puls: Debug Adapter

2023-12-20T16:01:52Z

Debug Adapter

← Older revision		Revision as of 18:01, 20 December 2023
Line 9:		Line 9:

	Visual Prolog Debugger is the IDE tool, which can be run with the '''Debug \| Run''' menu command, with the '''F5''' hot key, or with the [[Image:Ide_db_Run.png]] toolbar button.		Visual Prolog Debugger is the IDE tool, which can be run with the '''Debug \| Run''' menu command, with the '''F5''' hot key, or with the [[Image:Ide_db_Run.png]] toolbar button.

			== Debug Adapter ==

			{{Template:NonReleased}}

			Since version 11 Visual Prolog uses a '''Debug Adapter''' for the debugging process.

			A Debug Adapter is an independent program that connects to the debugged process. Instead of attaching directly to the debugged process, the IDE launches establishes communication with this Debug Adapter. This approach offers a practical advantage: it allows a 64-bit IDE to communicate with a 32-bit Debug Adapter, enabling the debugging of 32-bit processes alongside 64-bit programs.

			As a consequence in Visual Prolog 11 the IDE is always a 64-bit program.

			The communication between the IDE and the Debug Adapter adheres to the [https://microsoft.github.io/debug-adapter-protocol/ Debug Adapter Protocol] standard.

	== Generation of Debugging Information ==		== Generation of Debugging Information ==

Thomas Linder Puls: links

2013-06-13T14:46:00Z

links

← Older revision		Revision as of 16:46, 13 June 2013
Line 13:		Line 13:

	Generation of the information for Visual Prolog Debugger is controlled by copmiler's option		Generation of the information for Visual Prolog Debugger is controlled by copmiler's option
	{{ide\|~~IDE~~ Tools#Command Line Options\|/debug:full}}. By default, the Visual Prolog IDE always generates debugging information while compiling project modules.		{{ide\|Command Line Tools#Command Line Options\|/debug:full}}. By default, the Visual Prolog IDE always generates debugging information while compiling project modules.

	== Starting Visual Prolog Debugger ==		== Starting Visual Prolog Debugger ==

GalinaTchekmareva at 09:31, 18 April 2013

2013-04-18T09:31:11Z

← Older revision		Revision as of 11:31, 18 April 2013
Line 12:		Line 12:
	== Generation of Debugging Information ==		== Generation of Debugging Information ==

	Generation of the information for Visual Prolog Debugger is controlled by copmiler's option ~~[..\Command_Line_Tools\Command_Line_.htm~~#~~DEBug~~ /debug:full]. By default, the Visual Prolog IDE always generates debugging information while compiling project modules.		Generation of the information for Visual Prolog Debugger is controlled by copmiler's option
			{{ide\|IDE Tools#Command Line Options\|/debug:full}}. By default, the Visual Prolog IDE always generates debugging information while compiling project modules.

	== Starting Visual Prolog Debugger ==		== Starting Visual Prolog Debugger ==
Line 31:		Line 32:
	*:This command continues running the application. Issuing this command, when the IDE does not debug an application, builds (if needed) the application and starts its execution under the debugger. This command is often used in conjunction with setting of breakpoints.		*:This command continues running the application. Issuing this command, when the IDE does not debug an application, builds (if needed) the application and starts its execution under the debugger. This command is often used in conjunction with setting of breakpoints.
	*'''Run Skipping Soft Breakpoints (Ctrl+Shift+F10)'''		*'''Run Skipping Soft Breakpoints (Ctrl+Shift+F10)'''
	*:This command continues running the application without breaks at ''Soft Breakpoint'' (see ~~[Breakpoints_Window.htm~~ Breakpoints Window] for more details).		*:This command continues running the application without breaks at ''Soft Breakpoint'' (see {{ide\|Debugger#Breakpoints Window\|Breakpoints Window}} for more details).

	*'''Stop Debugging (Shift+F5)'''		*'''Stop Debugging (Shift+F5)'''
Line 131:		Line 132:

	If you have moved in the program source windows and have lost the ''Instruction Pointer'', then you can easy find it with the menu command '''Debug \| Go to Executing Predicate Source (Ctrl+E)'''. It sets the cursor to the line containing the currently executing predicate (to the line pointed by the ''Instruction Pointer'').		If you have moved in the program source windows and have lost the ''Instruction Pointer'', then you can easy find it with the menu command '''Debug \| Go to Executing Predicate Source (Ctrl+E)'''. It sets the cursor to the line containing the currently executing predicate (to the line pointed by the ''Instruction Pointer'').

	{{:ide/Debugger/Debugger Views}}		{{:ide/Debugger/Debugger Views}}

GalinaTchekmareva at 11:13, 28 March 2013

2013-03-28T11:13:46Z

@@ Line 98: / Line 98: @@
 *{{ide|Debugger#Breakpoints Window|BreakPoints}} ('''CTRL+Alt+B''')
 *{{ide|Debugger#Threads Window|Threads}} ('''CTRL+Alt+H''')]
-* [Modules_Window.htm Modules ]
+*{{ide|Debugger#Modules Window|Modules}}
 *{{ide|Debugger#Disassembly Window|Disassembly}} ('''CTRL+Alt+D''')]
-* [Registers_Window.htm Registers ('''CTRL+Alt+G''')]
+*{{ide|Debugger#Registers Window|Registers}} ('''CTRL+Alt+G''')]
-* [Memory_window.htm Memory Dump ('''CTRL+Alt+M''')]
+*{{ide|Debugger#Memory Dump Window|Memory Dump}} ('''CTRL+Alt+M''')]
 Also the following two windows, which are not only debugger windows (debugger views), can also be used while debugging:
@@ Line 107: / Line 107: @@
 *{{ide|Debugger#Project Tree|Project Tree}}
 *{{ide|Debugger#Source Code Windows|Source Code Windows}}
 {{:ide/Debugger/Debugger Views}}

GalinaTchekmareva at 09:56, 28 March 2013

2013-03-28T09:56:11Z

Show changes

GalinaTchekmareva at 13:47, 27 March 2013

2013-03-27T13:47:28Z

Show changes

GalinaTchekmareva at 13:40, 25 March 2013

2013-03-25T13:40:06Z

Show changes