Difference between revisions of "Developer documentation"
From Code::Blocks
m (add svn/git web interface address) |
(add section: catch crash call stack file and lines) |
||
| Line 73: | Line 73: | ||
* [[Wizard scripts|Creating a new project wizard]] | * [[Wizard scripts|Creating a new project wizard]] | ||
| + | |||
| + | == Debugging C::B == | ||
| + | |||
| + | When C::B crashed, it will generate a call-stack file "codeblocks.RPT", at the crash point, this is a text file, you can open it, if your C::B contains the debug information, it will have file and line information about each call. If it is a stripped version, but you have the debug version of C::B, you can try to run the [/index.php/topic,13129.msg88254.html#msg88254 Debugging made easier], this is a address2line UI interface works under Windows. | ||
Revision as of 10:03, 1 July 2012
Code repository
- Web-interface by ViewVC: http://svn.berlios.de/viewcvs/codeblocks/trunk/
- Subversion URL: http://svn.berlios.de/svnroot/repos/codeblocks/trunk
Mirror (Read-only; refreshed every 30 minutes.)
- Subversion URL: svn://cb.biplab.in/codeblocks/trunk
- Web-interface: http://cb.biplab.in/websvn/
- Git URL: git://cb.biplab.in/codeblocks.git
- Web-interface:http://cb.biplab.in/cgit/
Articles for Code::Blocks developers.
- Documentation
- User's manual in various formats and languages.
- Also see http://developer.berlios.de/projects/codeblocks/ (under the downloads section).
- Checkout the SDK documentation at http://developer.berlios.de/project/showfiles.php?group_id=5358 as CHM file(s).
- Code::Blocks uses Launchpad to coordinate translation efforts.
- The source code formatting style used in the Code::Blocks' source.
- How to add support for new syntax lighting schemes.
- Creating a diff file and then submitting it to the patch tracker.
- Information about unicode standards and how unicode is handled in Code::Blocks' source code.
- List of various development tips for Code::Blocks.
- Information about scripting Code::Blocks with Squirrel.
- Information about the architecture of Code::Blocks.
- Information about the Code::Blocks SDK events and how to work with them.
- Description of the format of each file Code::Blocks produces.
- Tips and trick for working with our version control system.
Plug-In development
- Creating a simple "Hello World" plugin
- Creating a Plug-in which modifies CB's Menus
- Creating a plugin that actually does something
- Linking the plugin to a Nightly Build
- Managing Plug-in Resources
Scripting
Using scripting to extend Code::Blocks' functionality
Debugging C::B
When C::B crashed, it will generate a call-stack file "codeblocks.RPT", at the crash point, this is a text file, you can open it, if your C::B contains the debug information, it will have file and line information about each call. If it is a stripped version, but you have the debug version of C::B, you can try to run the [/index.php/topic,13129.msg88254.html#msg88254 Debugging made easier], this is a address2line UI interface works under Windows.
