Debugging with Code::Blocks - Revision history

Obfuscated: /* Use 32bit CDB for 32bit programs and 64bit CDB for 64bit programs */

2016-11-09T18:40:56Z

Use 32bit CDB for 32bit programs and 64bit CDB for 64bit programs

2016-11-09T18:40:22Z

Use 32bit CDB for 32bit programs and 64bit CDB for 64bit programs

2014-04-12T08:41:08Z

Add Watches

2014-03-09T11:10:50Z

In 12.11 or latest nightly builds

2012-12-10T19:21:05Z

In latest nightly builds

2012-11-04T11:44:27Z

Added links.

2012-04-22T20:45:18Z

Double-clicking in the Call stack window

2012-04-22T20:44:17Z

Add Watches

2012-04-22T20:36:49Z

Add Watches

2012-01-24T07:31:29Z

Notes

@@ Line 68: / Line 68: @@
 It seems that debugging a 32bit program with 64bit CDB doesn't work on Windows 7, but 32bit CDB works perfectly.
-Note: This should no longer be the case with Code::Blocks' rev>=10920. See the ticket for details: [https://sourceforge.net/p/codeblocks/tickets/429/]
+Note: This should no longer be the case with Code::Blocks' rev>=10920. See the ticket for details: [https://sourceforge.net/p/codeblocks/tickets/429/ #429]
 ==Limits on the early version of MinGW==

@@ Line 67: / Line 67: @@
 ==Use 32bit CDB for 32bit programs and 64bit CDB for 64bit programs==
 It seems that debugging a 32bit program with 64bit CDB doesn't work on Windows 7, but 32bit CDB works perfectly.
 ==Limits on the early version of MinGW==

@@ Line 24: / Line 24: @@
 In the latest nightly builds the watches window has been redesigned and works differently that the one in 10.05.
-Currently there are two ways of adding watches in it:
+Currently there are three ways of adding watches in it:
 #Click in the empty last row in the watches window, type the name of the variable (or full expression) and hit enter.
 #While the debugger has stopped on a breakpoint select a variable name or full expression, right click to open the context menu and then select "Add watch 'expression'".
 The automatic inclusion of local variables and function arguments have being reimplemented in 13.12.

@@ Line 28: / Line 28: @@
 #While the debugger has stopped on a breakpoint select a variable name or full expression, right click to open the context menu and then select "Add watch 'expression'".
-The automatic inclusion of local variables and function arguments have not being reimplemented.
+The automatic inclusion of local variables and function arguments have being reimplemented in 13.12.
 =  Double-clicking in the Call stack window =

@@ Line 21: / Line 21: @@
 [[Image:Save watch.png]]
-== In latest nightly builds ==
+== In 12.11 or latest nightly builds ==
 In the latest nightly builds the watches window has been redesigned and works differently that the one in 10.05.

← Older revision		Revision as of 11:44, 4 November 2012
Line 76:		Line 76:

	...and place a breakpoint in "DebugCtorDtor" at the line "int i = 0;" . The debugger will break at that line. If you then step the debugger (Menu Debug => Next Line; or alternatively F7) you'll reach the code in the constructor/destructor ("is_initialized = true/false;").		...and place a breakpoint in "DebugCtorDtor" at the line "int i = 0;" . The debugger will break at that line. If you then step the debugger (Menu Debug => Next Line; or alternatively F7) you'll reach the code in the constructor/destructor ("is_initialized = true/false;").
		+
		+	==See also==
		+	* [[Debugger scripts]]
		+	* [[Pretty Printers]]

@@ Line 36: / Line 36: @@
 You have to right-click on a frame in the "call stack" debug window and select "Switch to this frame".
-[[File:DWCB_watches_01.png]
+[[File:DWCB_watches_01.png]]
 =Set Breakpoints=

@@ Line 12: / Line 12: @@
 =Add Watches=
 Open The Debugger Watches Window
@@ Line 25: / Line 26: @@
 [[File:DWCB_watches_01.png]]
 =Set Breakpoints=

@@ Line 45: / Line 45: @@
 ==Path with spaces==
 Breakpoints could not work if the path/folder you've placed your project contains spaces or other special characters. To be safe use English letters, digits and '_'.
 ==Update to the newest version of MinGW==