Developer documentation - Revision history

MichaelAgarkov at 22:46, 12 March 2025

2025-03-12T22:46:58Z

MichaelAgarkov: Returned my mirror back online.

2025-03-05T20:11:49Z

Returned my mirror back online.

Ollydbg: /* Debugging C::B */ distribute separate debug files

2025-02-12T09:26:41Z

Debugging C::B: distribute separate debug files

Ollydbg: /* Debugging C::B */ use the -femit-class-debug-always for debugging

2025-02-12T08:56:09Z

Debugging C::B: use the -femit-class-debug-always for debugging

Ollydbg: /* Debugging C::B */ add some debug tips

2025-02-05T09:49:58Z

Debugging C::B: add some debug tips

MichaelAgarkov: Removed my mirror since I'm no longer going to maintain it.

2024-11-21T16:10:53Z

Removed my mirror since I'm no longer going to maintain it.

MichaelAgarkov: Added my mirror of Code::Blocks to the list

2024-11-20T20:02:03Z

Added my mirror of Code::Blocks to the list

MichaelAgarkov: Added link to "Building Code::Blocks through GitHub Actions" article

2024-11-06T16:02:29Z

Added link to "Building Code::Blocks through GitHub Actions" article

Ollydbg: add new github mirror of our source code

2024-08-20T03:59:33Z

add new github mirror of our source code

Mgimenez: Make link to forum absolute

2022-11-13T11:07:17Z

Make link to forum absolute

@@ Line 8: / Line 8: @@
 '''Mirror by Carsten Arnholm''' (Read-only; )
 * Web-interface: https://github.com/arnholm/codeblocks_sfmirror
 * Git URL: see the above page.

@@ Line 8: / Line 8: @@
 '''Mirror by Carsten Arnholm''' (Read-only; )
 * Web-interface: https://github.com/arnholm/codeblocks_sfmirror
 * Git URL: see the above page.

← Older revision		Revision as of 09:26, 12 February 2025
Line 105:		Line 105:
	* to accelerate the debugging process for many plugins(when GDB load a lot of plugins with debug information, it will be slow), there is a special profile named "debug-plugin", a profile file is just a configure file named "debug-plugin.conf", when you start with this profile, you can exclude other plugins, and only load the plugins you needed, see discussion here: [https://forums.codeblocks.org/index.php/topic,25161.0.html How to exclude the other plugins when debugging]		* to accelerate the debugging process for many plugins(when GDB load a lot of plugins with debug information, it will be slow), there is a special profile named "debug-plugin", a profile file is just a configure file named "debug-plugin.conf", when you start with this profile, you can exclude other plugins, and only load the plugins you needed, see discussion here: [https://forums.codeblocks.org/index.php/topic,25161.0.html How to exclude the other plugins when debugging]
	* if you application or the debugee C::B is built against release version of wxWidgets library, how to debug the wxWidgets symbols, the method is to use the gcc's option "-femit-class-debug-always", see forum discussion here: [https://forums.codeblocks.org/index.php/topic,25731.0.html How to add gcc option "-femit-class-debug-always" to a single cpp file in cbp]		* if you application or the debugee C::B is built against release version of wxWidgets library, how to debug the wxWidgets symbols, the method is to use the gcc's option "-femit-class-debug-always", see forum discussion here: [https://forums.codeblocks.org/index.php/topic,25731.0.html How to add gcc option "-femit-class-debug-always" to a single cpp file in cbp]
		+	* to catch more debug information on the crash, we can distribute separate debug files, see discussion here: [https://forums.codeblocks.org/index.php/topic,25712.0.html new idea: ship the debug symbols in a separate file when we distribute C::B]

← Older revision		Revision as of 08:56, 12 February 2025
Line 104:		Line 104:
	* You can debug C::B under C::B (with the debugger plugin), also, you can link C::B to the debug version of wxWidgets library, so you can see whether a bug is located in C::B source code or wxWidgets' source code, see here: [https://forums.codeblocks.org/index.php/topic,17316.msg130972.html#msg130972 patch to build C::B against wx debug library]. You can use the project option plugin to change all the custom variable WX_SUFFIX from "u" to "ud" in the workspace, so that you can build C::B against wx debug library, see discussion here: [https://forums.codeblocks.org/index.php/topic,25959.0.html How to globally set the "custom variables" in the cbp files under a workspace].		* You can debug C::B under C::B (with the debugger plugin), also, you can link C::B to the debug version of wxWidgets library, so you can see whether a bug is located in C::B source code or wxWidgets' source code, see here: [https://forums.codeblocks.org/index.php/topic,17316.msg130972.html#msg130972 patch to build C::B against wx debug library]. You can use the project option plugin to change all the custom variable WX_SUFFIX from "u" to "ud" in the workspace, so that you can build C::B against wx debug library, see discussion here: [https://forums.codeblocks.org/index.php/topic,25959.0.html How to globally set the "custom variables" in the cbp files under a workspace].
	* to accelerate the debugging process for many plugins(when GDB load a lot of plugins with debug information, it will be slow), there is a special profile named "debug-plugin", a profile file is just a configure file named "debug-plugin.conf", when you start with this profile, you can exclude other plugins, and only load the plugins you needed, see discussion here: [https://forums.codeblocks.org/index.php/topic,25161.0.html How to exclude the other plugins when debugging]		* to accelerate the debugging process for many plugins(when GDB load a lot of plugins with debug information, it will be slow), there is a special profile named "debug-plugin", a profile file is just a configure file named "debug-plugin.conf", when you start with this profile, you can exclude other plugins, and only load the plugins you needed, see discussion here: [https://forums.codeblocks.org/index.php/topic,25161.0.html How to exclude the other plugins when debugging]
		+	* if you application or the debugee C::B is built against release version of wxWidgets library, how to debug the wxWidgets symbols, the method is to use the gcc's option "-femit-class-debug-always", see forum discussion here: [https://forums.codeblocks.org/index.php/topic,25731.0.html How to add gcc option "-femit-class-debug-always" to a single cpp file in cbp]

← Older revision		Revision as of 09:49, 5 February 2025
Line 102:		Line 102:

	* When C::B crashes, it will generate a call-stack file "codeblocks.RPT", at the crash point (see [[FAQ-Compiling_(general)#Q: How do I report a compilation problem on the forums?\|this]] for more information). This is a text file that you can open; if your C::B contains the debug information, it will have file and line information about each call. If your C::B is a stripped version, but you have the debug version of C::B, you can try to run the [https://forums.codeblocks.org/index.php/topic,13129.msg88254.html#msg88254 Debugging made easier], this is an address2line UI interface that works under Windows.		* When C::B crashes, it will generate a call-stack file "codeblocks.RPT", at the crash point (see [[FAQ-Compiling_(general)#Q: How do I report a compilation problem on the forums?\|this]] for more information). This is a text file that you can open; if your C::B contains the debug information, it will have file and line information about each call. If your C::B is a stripped version, but you have the debug version of C::B, you can try to run the [https://forums.codeblocks.org/index.php/topic,13129.msg88254.html#msg88254 Debugging made easier], this is an address2line UI interface that works under Windows.
−	* You can debug C::B under C::B (with the debugger plugin), also, you can link C::B to the debug version of wxWidgets library, so you can see whether a bug is located in C::B source code or wxWidgets' source code, see here: [https://forums.codeblocks.org/index.php/topic,17316.msg130972.html#msg130972 patch to build C::B against wx debug library]	+	* You can debug C::B under C::B (with the debugger plugin), also, you can link C::B to the debug version of wxWidgets library, so you can see whether a bug is located in C::B source code or wxWidgets' source code, see here: [https://forums.codeblocks.org/index.php/topic,17316.msg130972.html#msg130972 patch to build C::B against wx debug library]. You can use the project option plugin to change all the custom variable WX_SUFFIX from "u" to "ud" in the workspace, so that you can build C::B against wx debug library, see discussion here: [https://forums.codeblocks.org/index.php/topic,25959.0.html How to globally set the "custom variables" in the cbp files under a workspace].
		+	* to accelerate the debugging process for many plugins(when GDB load a lot of plugins with debug information, it will be slow), there is a special profile named "debug-plugin", a profile file is just a configure file named "debug-plugin.conf", when you start with this profile, you can exclude other plugins, and only load the plugins you needed, see discussion here: [https://forums.codeblocks.org/index.php/topic,25161.0.html How to exclude the other plugins when debugging]

← Older revision		Revision as of 16:02, 6 November 2024
Line 96:		Line 96:

	If you want to create a SVN style patch from git, see: [https://forums.codeblocks.org/index.php/topic,19391.msg132530.html#msg132530 This forum post].		If you want to create a SVN style patch from git, see: [https://forums.codeblocks.org/index.php/topic,19391.msg132530.html#msg132530 This forum post].
		+
		+	It's possible to build Code::Blocks through GitHub Actions, see [https://wiki.codeblocks.org/index.php/Building_Code::Blocks_through_GitHub_Actions Building Code::Blocks through GitHub Actions].

	== Debugging C::B ==		== Debugging C::B ==

@@ Line 5: / Line 5: @@
 * Web-interface by ViewVC: http://sourceforge.net/p/codeblocks/code/log/
 * Subversion URL: <nowiki>svn://svn.code.sf.net/p/codeblocks/code/trunk</nowiki> or <nowiki>http://svn.code.sf.net/p/codeblocks/code/trunk</nowiki>
 '''Mirror by biplab''' (Read-only; refreshed every 10 minutes. As 2022-09-12, it looks dead.)

@@ Line 36: / Line 36: @@
 * '''[http://launchpad.net/products/codeblocks/ Old Translation page]'''
 * '''[http://launchpad.net/products/codeblocks-gd/ New Translation page]'''
-:See also [/index.php/topic,1022.msg159075.html#msg159075 Code::Blocks' translation]
+:See also [https://forums.codeblocks.org/index.php/topic,1022.msg159075.html#msg159075 Code::Blocks' translation]
 * '''[[Coding style]]'''