Debugger scripts - Revision history

MortenMacFly: /* Basic principle of the debugger script */

2013-01-12T12:59:45Z

Basic principle of the debugger script

← Older revision		Revision as of 12:59, 12 January 2013
Line 5:		Line 5:
	[[image:Debuggercommand.png]]		[[image:Debuggercommand.png]]

	Look at the image above, this will give a ~~belief~~ introduction of how the debugger script works. For example, you want to view the variable "msg". There are two handshake between the debugger plugin and gdb.		Look at the image above, this will give a brief introduction of how the debugger script works. For example, you want to view the variable "msg". There are two handshake between the debugger plugin and gdb.

	First, the debugger plugin sends a command to gdb to query the type of msg		First, the debugger plugin sends a command to gdb to query the type of msg

Pecan: /* Script functions */

2011-10-31T12:31:47Z

Script functions

← Older revision		Revision as of 12:31, 31 October 2011
Line 42:		Line 42:
	This script is called by Code::Blocks at two places:		This script is called by Code::Blocks at two places:

	# when GDB is launched. It calls the script function RegisterTypes() to register all user-defined types ~~with~~ Code::Blocks' debugger.		# when GDB is launched. It calls the script function RegisterTypes() to register all user-defined types known by the Code::Blocks' debugger.
	# whenever GDB encounters your variable type, it calls the script functions specific to this datatype (registered in RegisterTypes() - more on that below).		# whenever GDB encounters your variable type, it calls the script functions specific to this datatype (registered in RegisterTypes() - more on that below).

Line 68:		Line 68:
	So, in the above script code, the "STL String" (just a name - doesn't matter what) type is registered, providing a regular expression string for the debugger plugin to match against and, finally, it provides the names of the two mandatory functions needed for each registered type:		So, in the above script code, the "STL String" (just a name - doesn't matter what) type is registered, providing a regular expression string for the debugger plugin to match against and, finally, it provides the names of the two mandatory functions needed for each registered type:

	# evaluation function: this must return a command understood by the actual debugger (GDB in this case) ~~and it issues it~~.		# evaluation function: this must return a command understood by the actual debugger (GDB in this case). For the "STL string", the evaluate function returns an GDB "output" command which will be executed by the GDB debugger.
	# parser function: once the debugger runs the command returned by the evaluation function, it passes its result to this function for further processing. What this function returns, is what is actually ~~returned to the user~~ (usually in the watches window or in a tooltip).		# parser function: once the debugger runs the command returned by the evaluation function, it passes its result to this function for further processing. What this function returns, is what is actually diplayed by CodeBlocks (usually in the watches window or in a tooltip).

Pecan: /* Basic principle of the debugger script */

2011-10-31T12:20:34Z

Basic principle of the debugger script

← Older revision		Revision as of 12:20, 31 October 2011
Line 28:		Line 28:
	</pre>		</pre>

	Finally, the value ~~was~~ shown in the watch window		Finally, the value is shown in the watch window

	==Script functions==		==Script functions==

Pecan: /* Basic principle of the debugger script */

2011-10-31T12:19:26Z

Basic principle of the debugger script

← Older revision		Revision as of 12:19, 31 October 2011
Line 7:		Line 7:
	Look at the image above, this will give a belief introduction of how the debugger script works. For example, you want to view the variable "msg". There are two handshake between the debugger plugin and gdb.		Look at the image above, this will give a belief introduction of how the debugger script works. For example, you want to view the variable "msg". There are two handshake between the debugger plugin and gdb.

	First, the debugger plugin ~~send~~ a command to gdb~~, qurey~~ the type of msg		First, the debugger plugin sends a command to gdb to query the type of msg
	<pre>		<pre>
	whatis msg		whatis msg
Line 15:		Line 15:
	type = wxString		type = wxString
	</pre>		</pre>
	Secondly, the debugger ~~check the~~ wxString is already registered, and ~~send~~ the command		Secondly, the debugger checks that wxString is already registered, and sends the command
	<pre>		<pre>
	output /c msg.m_pchData[0]@((wxStringData*)msg.m_pchData-1)->nDataLength		output /c msg.m_pchData[0]@((wxStringData*)msg.m_pchData-1)->nDataLength
	</pre>		</pre>
	Then, gdb replies the string below:		Then, gdb replies with the string below:
	<pre>		<pre>
	{119 'w', 120 'x', 87 'W', 105 'i', 100 'd', 103 'g', 101 'e', 116 't',		{119 'w', 120 'x', 87 'W', 105 'i', 100 'd', 103 'g', 101 'e', 116 't',

Ollydbg: /* See also */ debug Qstring forum discussion

2009-11-25T11:58:29Z

See also: debug Qstring forum discussion

← Older revision		Revision as of 11:58, 25 November 2009
Line 113:		Line 113:

	I suggest you study how wxString is registered in that same file, as a more complex example.		I suggest you study how wxString is registered in that same file, as a more complex example.

			== Links ==

			#[/index.php/topic,11184.msg76200.html#msg76200 Debugging QString]

	== See also ==		== See also ==

	* [[Scripting commands]]		* [[Scripting commands]]

Ollydbg: /* Basic principle of the debugger script */

2009-10-14T13:05:22Z

Basic principle of the debugger script

← Older revision		Revision as of 13:05, 14 October 2009
Line 28:		Line 28:
	</pre>		</pre>

			Finally, the value was shown in the watch window

			==Script functions==
	Debugger scripts are similar to [http://www.codeproject.com/csharp/ImageVisualizer.asp Visual Studio Debugger Visualizer]. It allows you to write a small piece of code that gets executed by the debugger whenever you try to view a specific type of variables and can be used to show custom text with the important information you need in it.		Debugger scripts are similar to [http://www.codeproject.com/csharp/ImageVisualizer.asp Visual Studio Debugger Visualizer]. It allows you to write a small piece of code that gets executed by the debugger whenever you try to view a specific type of variables and can be used to show custom text with the important information you need in it.

Ollydbg: add image and some description

2009-10-14T13:03:02Z

add image and some description

← Older revision		Revision as of 13:03, 14 October 2009
Line 1:		Line 1:
	[[Category:Scripting Code::Blocks]]		[[Category:Scripting Code::Blocks]]

			==Basic principle of the debugger script==

			[[image:Debuggercommand.png]]

			Look at the image above, this will give a belief introduction of how the debugger script works. For example, you want to view the variable "msg". There are two handshake between the debugger plugin and gdb.

			First, the debugger plugin send a command to gdb, qurey the type of msg
			<pre>
			whatis msg
			</pre>
			then, the gdb will return the type
			<pre>
			type = wxString
			</pre>
			Secondly, the debugger check the wxString is already registered, and send the command
			<pre>
			output /c msg.m_pchData[0]@((wxStringData*)msg.m_pchData-1)->nDataLength
			</pre>
			Then, gdb replies the string below:
			<pre>
			{119 'w', 120 'x', 87 'W', 105 'i', 100 'd', 103 'g', 101 'e', 116 't',
			115 's', 32 ' ', 50 '2', 46 '.', 56 '8', 46 '.', 49 '1', 48 '0', 45 '-',
			87 'W', 105 'i', 110 'n', 100 'd', 111 'o', 119 'w', 115 's', 45 '-',
			85 'U', 110 'n', 105 'i', 99 'c', 111 'o', 100 'd', 101 'e', 32 ' ',
			98 'b', 117 'u', 105 'i', 108 'l', 100 'd'}
			</pre>

	Debugger scripts are similar to [http://www.codeproject.com/csharp/ImageVisualizer.asp Visual Studio Debugger Visualizer]. It allows you to write a small piece of code that gets executed by the debugger whenever you try to view a specific type of variables and can be used to show custom text with the important information you need in it.		Debugger scripts are similar to [http://www.codeproject.com/csharp/ImageVisualizer.asp Visual Studio Debugger Visualizer]. It allows you to write a small piece of code that gets executed by the debugger whenever you try to view a specific type of variables and can be used to show custom text with the important information you need in it.

Artojon: removed extra category

2006-11-11T17:40:01Z

removed extra category

← Older revision		Revision as of 17:40, 11 November 2006
Line 1:		Line 1:
	~~[[Category:Code::Blocks_Documentation]]~~
	[[Category:Scripting Code::Blocks]]		[[Category:Scripting Code::Blocks]]

Sethjackson at 13:44, 9 July 2006

2006-07-09T13:44:32Z

← Older revision		Revision as of 13:44, 9 July 2006
Line 84:		Line 84:

	I suggest you study how wxString is registered in that same file, as a more complex example.		I suggest you study how wxString is registered in that same file, as a more complex example.


	~~That's all!~~

	== See also ==		== See also ==

	* [[Scripting commands]]		* [[Scripting commands]]

Artojon: wikify

2006-07-07T19:00:27Z

wikify

← Older revision		Revision as of 19:00, 7 July 2006
Line 1:		Line 1:
			[[Category:Code::Blocks_Documentation]]
			[[Category:Scripting Code::Blocks]]

	Debugger scripts are similar to [http://www.codeproject.com/csharp/ImageVisualizer.asp Visual Studio Debugger Visualizer]. It allows you to write a small piece of code that gets executed by the debugger whenever you try to view a specific type of variables and can be used to show custom text with the important information you need in it.		Debugger scripts are similar to [http://www.codeproject.com/csharp/ImageVisualizer.asp Visual Studio Debugger Visualizer]. It allows you to write a small piece of code that gets executed by the debugger whenever you try to view a specific type of variables and can be used to show custom text with the important information you need in it.

Line 85:		Line 88:
	That's all!		That's all!

			== See also ==

	~~See also:~~ [[~~scripting~~ commands~~]].~~		* [[Scripting commands]]

	~~Back to [[Scripting_Code::Blocks\|scripting index]].~~

	~~[[Category:Code::Blocks_Documentation~~]]