The Debugger - Revision history

Badge at 22:30, 23 May 2009

2009-05-23T22:30:36Z

← Older revision		Revision as of 22:30, 23 May 2009
Line 44:		Line 44:
	To start the Debugger you’ll need to run CosD.exe, then attach it to your IB program. The Debugger uses Windows messaging to talk to your program. Note: Since you need access to the system’s console to run an .exe, the Debugger is not available if you are a Comet Anywhere client.		To start the Debugger you’ll need to run CosD.exe, then attach it to your IB program. The Debugger uses Windows messaging to talk to your program. Note: Since you need access to the system’s console to run an .exe, the Debugger is not available if you are a Comet Anywhere client.

-	[[Image:~~debugger1~~.jpg\|400px\|center]]	+	[[Image:Debugger1.jpg\|400px\|center]]

Badge at 22:20, 23 May 2009

2009-05-23T22:20:40Z

← Older revision		Revision as of 22:20, 23 May 2009
Line 65:		Line 65:

	[[Image:DebuggerWatch.jpg]]		[[Image:DebuggerWatch.jpg]]
-
-	~~[[Image:security.jpg]]~~

	To change the contents of a variable simply double click on its name in the Watch Window. A dialog will popup and prompt you for the new value. String variables that contain hex values can also be viewed and edited. To change the display to hex, right click on the variable’s name and select “View As Hex”. To switch back, select “View As String”.		To change the contents of a variable simply double click on its name in the Watch Window. A dialog will popup and prompt you for the new value. String variables that contain hex values can also be viewed and edited. To change the display to hex, right click on the variable’s name and select “View As Hex”. To switch back, select “View As String”.

Badge at 22:19, 23 May 2009

2009-05-23T22:19:57Z

← Older revision		Revision as of 22:19, 23 May 2009
Line 65:		Line 65:

	[[Image:DebuggerWatch.jpg]]		[[Image:DebuggerWatch.jpg]]
		+
		+	[[Image:security.jpg]]

	To change the contents of a variable simply double click on its name in the Watch Window. A dialog will popup and prompt you for the new value. String variables that contain hex values can also be viewed and edited. To change the display to hex, right click on the variable’s name and select “View As Hex”. To switch back, select “View As String”.		To change the contents of a variable simply double click on its name in the Watch Window. A dialog will popup and prompt you for the new value. String variables that contain hex values can also be viewed and edited. To change the display to hex, right click on the variable’s name and select “View As Hex”. To switch back, select “View As String”.

Jim at 04:48, 19 August 2008

2008-08-19T04:48:21Z

← Older revision		Revision as of 04:48, 19 August 2008
Line 44:		Line 44:
	To start the Debugger you’ll need to run CosD.exe, then attach it to your IB program. The Debugger uses Windows messaging to talk to your program. Note: Since you need access to the system’s console to run an .exe, the Debugger is not available if you are a Comet Anywhere client.		To start the Debugger you’ll need to run CosD.exe, then attach it to your IB program. The Debugger uses Windows messaging to talk to your program. Note: Since you need access to the system’s console to run an .exe, the Debugger is not available if you are a Comet Anywhere client.

-	[[Image:debugger1.jpg \| ~~Width 100px~~]]	+	[[Image:debugger1.jpg\|400px\|center]]
		+

	Don’t be overwhelmed by the number of windows displayed. The Debugger is a very powerful tool and can display many different types of information about the flow of your program. However, you can change the display to show only the windows you need. Many programs can be debugged using only a couple of these windows.		Don’t be overwhelmed by the number of windows displayed. The Debugger is a very powerful tool and can display many different types of information about the flow of your program. However, you can change the display to show only the windows you need. Many programs can be debugged using only a couple of these windows.

Jim at 04:25, 19 August 2008

2008-08-19T04:25:43Z

← Older revision		Revision as of 04:25, 19 August 2008
Line 44:		Line 44:
	To start the Debugger you’ll need to run CosD.exe, then attach it to your IB program. The Debugger uses Windows messaging to talk to your program. Note: Since you need access to the system’s console to run an .exe, the Debugger is not available if you are a Comet Anywhere client.		To start the Debugger you’ll need to run CosD.exe, then attach it to your IB program. The Debugger uses Windows messaging to talk to your program. Note: Since you need access to the system’s console to run an .exe, the Debugger is not available if you are a Comet Anywhere client.

-	[[Image:debugger1.jpg\|~~200px~~]]	+	[[Image:debugger1.jpg \| Width 100px]]

	Don’t be overwhelmed by the number of windows displayed. The Debugger is a very powerful tool and can display many different types of information about the flow of your program. However, you can change the display to show only the windows you need. Many programs can be debugged using only a couple of these windows.		Don’t be overwhelmed by the number of windows displayed. The Debugger is a very powerful tool and can display many different types of information about the flow of your program. However, you can change the display to show only the windows you need. Many programs can be debugged using only a couple of these windows.

Jim at 04:05, 19 August 2008

2008-08-19T04:05:44Z

← Older revision		Revision as of 04:05, 19 August 2008
Line 44:		Line 44:
	To start the Debugger you’ll need to run CosD.exe, then attach it to your IB program. The Debugger uses Windows messaging to talk to your program. Note: Since you need access to the system’s console to run an .exe, the Debugger is not available if you are a Comet Anywhere client.		To start the Debugger you’ll need to run CosD.exe, then attach it to your IB program. The Debugger uses Windows messaging to talk to your program. Note: Since you need access to the system’s console to run an .exe, the Debugger is not available if you are a Comet Anywhere client.

-	[[Image:debugger1.jpg]]	+	[[Image:debugger1.jpg\|200px]]

	Don’t be overwhelmed by the number of windows displayed. The Debugger is a very powerful tool and can display many different types of information about the flow of your program. However, you can change the display to show only the windows you need. Many programs can be debugged using only a couple of these windows.		Don’t be overwhelmed by the number of windows displayed. The Debugger is a very powerful tool and can display many different types of information about the flow of your program. However, you can change the display to show only the windows you need. Many programs can be debugged using only a couple of these windows.

SteveA: /* Windows Messages */

2008-08-18T19:30:29Z

Windows Messages

← Older revision		Revision as of 19:30, 18 August 2008
Line 93:		Line 93:
	The values displayed represent the following API variables:		The values displayed represent the following API variables:

-	* Func:cosOD.Function$	+	* Func: cosOD.Function$
-	* Cmd:cosOD.Cmd$	+	* Cmd: cosOD.Cmd$
-	* Flags:cosOD.Flags$	+	* Flags: cosOD.Flags$
-	* nID:cosOD.nID$	+	* nID: cosOD.nID$
-	* Msg:cosOD.Msg$	+	* Msg: cosOD.Msg$
-	* wParam:cosOD.wParam$	+	* wParam: cosOD.wParam$
-	* hDlg:cosOD.hDlg$	+	* hDlg: cosOD.hDlg$

	As an alternative to the Window Messages Window, you could just add the listed variables to your watch list. But, if you find this method easier and you really need to debug down to this level, here’s how you can invoke this display.		As an alternative to the Window Messages Window, you could just add the listed variables to your watch list. But, if you find this method easier and you really need to debug down to this level, here’s how you can invoke this display.

SteveA: /* Windows Messages */

2008-08-18T19:29:44Z

Windows Messages

← Older revision		Revision as of 19:29, 18 August 2008
Line 89:		Line 89:
	However, if you’re having a problem with one of the Windows calls, this is one way to view the contents of the API variables being used.		However, if you’re having a problem with one of the Windows calls, this is one way to view the contents of the API variables being used.

-	[[Image:~~DebuggerWindowsMessage~~.jpg]]	+	[[Image:DebuggerWindowsMessages.jpg]]

	The values displayed represent the following API variables:		The values displayed represent the following API variables:

SteveA: /* Windows Messages */

2008-08-18T19:27:56Z

Windows Messages

← Older revision		Revision as of 19:27, 18 August 2008
Line 89:		Line 89:
	However, if you’re having a problem with one of the Windows calls, this is one way to view the contents of the API variables being used.		However, if you’re having a problem with one of the Windows calls, this is one way to view the contents of the API variables being used.

-	[[Image:~~DebuggerWindowsMessages~~.jpg]]	+	[[Image:DebuggerWindowsMessage.jpg]]

	The values displayed represent the following API variables:		The values displayed represent the following API variables:

SteveA: /* Windows Messages */

2008-08-18T19:26:55Z

Windows Messages

← Older revision		Revision as of 19:26, 18 August 2008
Line 89:		Line 89:
	However, if you’re having a problem with one of the Windows calls, this is one way to view the contents of the API variables being used.		However, if you’re having a problem with one of the Windows calls, this is one way to view the contents of the API variables being used.

-	~~<!--~~[[Image:]]~~-->~~	+	[[Image:DebuggerWindowsMessages.jpg]]

	The values displayed represent the following API variables:		The values displayed represent the following API variables: