More Debugger - Revision history

Badge: /* Editing Breakpoints */

2009-06-11T21:25:48Z

Editing Breakpoints

2009-06-11T21:25:26Z

Stepping Into or Over a Subroutine

← Older revision		Revision as of 21:25, 11 June 2009
Line 155:		Line 155:
	[[Image:Debug11.jpg]]		[[Image:Debug11.jpg]]

-	== Stepping Into or Over a Subroutine ==	+	=== Stepping Into or Over a Subroutine ===

2009-06-11T21:24:15Z

Quick Watch

2009-06-11T21:23:54Z

Watched Variables

2009-06-11T21:23:31Z

Source Code Display

← Older revision		Revision as of 21:23, 11 June 2009
Line 96:		Line 96:
	* To stop whenever your program encounters an unhandled exception, check the "Unhandled Exceptions" box		* To stop whenever your program encounters an unhandled exception, check the "Unhandled Exceptions" box

-	== Source Code Display ==	+	=== Source Code Display ===

2009-06-11T21:20:46Z

2009-06-11T20:01:21Z

Window Messages

← Older revision		Revision as of 20:01, 11 June 2009
Line 310:		Line 310:

	The "Window Messages" window show messages generated by the Windows Development Library (WDL). This feature must be enabled in your code by setting the following symbolic constants:		The "Window Messages" window show messages generated by the Windows Development Library (WDL). This feature must be enabled in your code by setting the following symbolic constants:
-	SET NEW.TRACE = 1 ! Enable tracing	+	SET NEW.TRACE = 1 ! Enable tracing
-	SET TRACE.CALLS = 1 ! Show outgoing messages	+	SET TRACE.CALLS = 1 ! Show outgoing messages
-	SET TRACE.RECEIVE = 1 ! Show incoming messages	+	SET TRACE.RECEIVE = 1 ! Show incoming messages

	Also, in order for the Windows message trace feature to work, you must first enable the cosTrace variable. This is a feature that allows the user to control when the messages are displayed.		Also, in order for the Windows message trace feature to work, you must first enable the cosTrace variable. This is a feature that allows the user to control when the messages are displayed.
-	cosTrace = TRUE ! Enable trace messages	+	cosTrace = TRUE ! Enable trace messages

	The following sample display comes from the DIRECT.IBS,DLG program.		The following sample display comes from the DIRECT.IBS,DLG program.
		+
		+	[[Image:Debug22.jpg]]

2009-06-11T20:00:32Z

Include Files

← Older revision		Revision as of 20:00, 11 June 2009
Line 299:		Line 299:

	If your program contains include files (i.e., usefiles), you can view any of them by choosing the file name on the "Window" menu. The contents of the include file are displayed in the source code window.		If your program contains include files (i.e., usefiles), you can view any of them by choosing the file name on the "Window" menu. The contents of the include file are displayed in the source code window.
-		+	[[Image:Debug21.jpg]]

	If your program executes instructions in an executable include file, that file is automatically displayed in the source code window as you step through the code.		If your program executes instructions in an executable include file, that file is automatically displayed in the source code window as you step through the code.

-	Note that the debugger requires all source and include files to be text files.	+	Note that the debugger requires all source and include files to be text files.
-		+

	== Window Messages ==		== Window Messages ==

2009-06-11T19:59:45Z

Call Stack

← Older revision		Revision as of 19:59, 11 June 2009
Line 289:		Line 289:

	The Call Stack window displays the subroutine stack. This list is displayed in inverted order, with the most recent subroutine call shown at the top of the list.		The Call Stack window displays the subroutine stack. This list is displayed in inverted order, with the most recent subroutine call shown at the top of the list.
-	~~The following example shows the program name that is running ("TEST" on "BAM") and shows that the program is currently nested two subroutines deep ("ROUTINE1" followed by "ROUTINE2")~~
-
-

		+	The following example shows the program name that is running ("TEST" on "BAM") and shows that the program is currently nested two subroutines deep ("ROUTINE1" followed by "ROUTINE2")

		+	[[Image:Debug20.jpg]]

	== Include Files ==		== Include Files ==

2009-06-11T19:58:59Z

Go to IP

← Older revision		Revision as of 19:58, 11 June 2009
Line 281:		Line 281:
	While looking at the source code in the "Source" window, you can instruct the debugger to display the source line where the instruction pointer (IP) is located. To use this feature, use one of the following methods:		While looking at the source code in the "Source" window, you can instruct the debugger to display the source line where the instruction pointer (IP) is located. To use this feature, use one of the following methods:

-	Select "Goto IP" on the "Debug" menu	+	* Select "Goto IP" on the "Debug" menu
-	Press Alt+F5	+	* Press Alt+F5

	== Call Stack ==		== Call Stack ==