WindowsGuestDrivers/UpdatedGuestDebugging - Revision history

Vrozenfe at 18:29, 13 November 2011

2011-11-13T18:29:14Z

← Older revision		Revision as of 14:29, 13 November 2011
Line 78:		Line 78:
	#include "virtio_test_utils.h"		#include "virtio_test_utils.h"

	VOID DriverUnload(IN PDRIVER_OBJECT DeviceObject);		VOID DriverUnload( IN PDRIVER_OBJECT DeviceObject );

	ULONG DriverEntry( IN PDRIVER_OBJECT& DriverObject, IN PVOID RegistryPath ) {		ULONG DriverEntry( IN PDRIVER_OBJECT DriverObject, IN PVOID RegistryPath ) {
	ULONG initResult = 0;		ULONG initResult = 0;

Vrozenfe at 18:27, 13 November 2011

2011-11-13T18:27:00Z

← Older revision		Revision as of 14:27, 13 November 2011
Line 80:		Line 80:
	VOID DriverUnload(IN PDRIVER_OBJECT DeviceObject);		VOID DriverUnload(IN PDRIVER_OBJECT DeviceObject);

	ULONG; DriverEntry( IN PDRIVER_OBJECT&; DriverObject, IN PVOID; RegistryPath ) {		ULONG DriverEntry( IN PDRIVER_OBJECT& DriverObject, IN PVOID RegistryPath ) {
	ULONG initResult = 0;		ULONG initResult = 0;

Line 90:		Line 90:
	}		}

	VOID DriverUnload( IN PDRIVER_OBJECT DeviceObject ){		VOID DriverUnload( IN PDRIVER_OBJECT DeviceObject ) {
	DbgPrint("Driver Unload successfully\! \n");		DbgPrint("Driver Unload successfully\! \n");
	}		}

Caobingbu at 07:21, 11 November 2011

2011-11-11T07:21:22Z

← Older revision		Revision as of 03:21, 11 November 2011
Line 158:		Line 158:

	=References=		=References=
	*1).[[WindowsGuestDrivers/GuestDebugging \| Guest Debugging ~~on this site~~]]		*1).[[WindowsGuestDrivers/GuestDebugging \| Guest Debugging]]
	*2).http://msdn.microsoft.com/library/windows/hardware/gg507680		*2).http://msdn.microsoft.com/library/windows/hardware/gg507680
	*3).Debugging tools for Windows HELP		*3).Debugging tools for Windows HELP

Caobingbu at 09:32, 10 November 2011

2011-11-10T09:32:19Z

← Older revision		Revision as of 05:32, 10 November 2011
Line 123:		Line 123:
	<br>And the related source file will be opened to view.		<br>And the related source file will be opened to view.
	<br>You can see the breakpoints position with highlight label in the source code		<br>You can see the breakpoints position with highlight label in the source code
	[[Image:~~sourcecode~~.png]]		[[Image:breakpoint.png]]
	also can watch the variables value,check the callstacks etc. All behaviors of WinDbg are similar to other debuggers.		also can watch the variables value,check the callstacks etc. All behaviors of WinDbg are similar to other debuggers.
	[[Image:variable.png]]		[[Image:variable.png]]

Caobingbu at 09:30, 10 November 2011

2011-11-10T09:30:36Z

← Older revision		Revision as of 05:30, 10 November 2011
Line 117:		Line 117:

	You can use <tt>"bl"</tt> to watch breakpoints set.		You can use <tt>"bl"</tt> to watch breakpoints set.
	~~[[Image:breakpoint.png]]~~
	<br>F5,continue.		<br>F5,continue.
	<br>Using tool [DriverStudio] to load,start,stop the driver on target.		<br>Using tool [DriverStudio] to load,start,stop the driver on target.

Caobingbu at 09:29, 10 November 2011

2011-11-10T09:29:37Z

← Older revision		Revision as of 05:29, 10 November 2011
Line 102:		Line 102:

	<tt>viotest>build -cCzg</tt>		<tt>viotest>build -cCzg</tt>
			[[Image:build.png]]

	After build completely,the driver(<tt>viotest.sys,viotest.inf</tt>) will be exported into the <tt>...\viotest\objchk_wxp_x86\i386\</tt>.		After build completely,the driver(<tt>viotest.sys,viotest.inf</tt>) will be exported into the <tt>...\viotest\objchk_wxp_x86\i386\</tt>.
Line 116:		Line 117:

	You can use <tt>"bl"</tt> to watch breakpoints set.		You can use <tt>"bl"</tt> to watch breakpoints set.
			[[Image:breakpoint.png]]
	<br>F5,continue.		<br>F5,continue.
	<br>Using tool [DriverStudio] to load,start,stop the driver on target.		<br>Using tool [DriverStudio] to load,start,stop the driver on target.
Line 121:		Line 123:
	<br>Meanwhile,the WinDbg will hit the breakpoint at <tt>viotest.c:DriverEntry()</tt>.		<br>Meanwhile,the WinDbg will hit the breakpoint at <tt>viotest.c:DriverEntry()</tt>.
	<br>And the related source file will be opened to view.		<br>And the related source file will be opened to view.
	<br>You can see the breakpoints position with highlight label in the source code ~~and~~ watch the variables value,check the callstacks etc. All behaviors of WinDbg are similar to other debuggers.		<br>You can see the breakpoints position with highlight label in the source code
			[[Image:sourcecode.png]]
			also can watch the variables value,check the callstacks etc. All behaviors of WinDbg are similar to other debuggers.
			[[Image:variable.png]]
			[[Image:stack.png]]
	<br>The debug message will be show in the WinDbg.		<br>The debug message will be show in the WinDbg.

Line 138:		Line 144:
	==Other Debug Method==		==Other Debug Method==
	* Using Debug message(print):		* Using Debug message(print):
	:The message can be viewed by another tool [http://technet.microsoft.com/en-us/sysinternals/bb896647 DebugView],it can be used in target guest(without WinDbg) only environment to debug the driver with the <tt>DbgPrint()</tt> debug message.		:The message can be viewed by another tool [http://technet.microsoft.com/en-us/sysinternals/bb896647 DebugView],it can be used in target guest(without WinDbg) only environment to debug the driver with the <tt>DbgPrint()</tt> debug message. It is also a available method to debug the driver.
	It is also a available method to debug the driver.

	* Using crash dump (kernel memory dump)with WinDbg		* Using crash dump (kernel memory dump)with WinDbg

Caobingbu at 09:11, 10 November 2011

2011-11-10T09:11:23Z

← Older revision		Revision as of 05:11, 10 November 2011
Line 138:		Line 138:
	==Other Debug Method==		==Other Debug Method==
	* Using Debug message(print):		* Using Debug message(print):
	The message can be viewed by another tool [http://technet.microsoft.com/en-us/sysinternals/bb896647 DebugView],it can be used in target guest(without WinDbg) only environment to debug the driver with the <tt>DbgPrint()</tt> debug message.		:The message can be viewed by another tool [http://technet.microsoft.com/en-us/sysinternals/bb896647 DebugView],it can be used in target guest(without WinDbg) only environment to debug the driver with the <tt>DbgPrint()</tt> debug message.
	It is also a available method to debug the driver.		It is also a available method to debug the driver.

	* Using crash dump (kernel memory dump)with WinDbg		* Using crash dump (kernel memory dump)with WinDbg
	~~<pre style="color~~:~~red">~~
	TBD.		:''TBD.''
	~~</pre>~~

	==Problems may be encountered==		==Problems may be encountered==

Caobingbu at 09:10, 10 November 2011

2011-11-10T09:10:23Z

← Older revision		Revision as of 05:10, 10 November 2011
Line 56:		Line 56:
	Add <tt>-serial tcp:127.0.0.1:4445</tt> to connect to the host by virtual serial,port is same to the server.		Add <tt>-serial tcp:127.0.0.1:4445</tt> to connect to the host by virtual serial,port is same to the server.
	<br>When start up,if Windows XP,2003 or 2000,edit <tt>c:\boot.ini</tt> and duplicate the default boot line,at the end of the duplicated boot line add		<br>When start up,if Windows XP,2003 or 2000,edit <tt>c:\boot.ini</tt> and duplicate the default boot line,at the end of the duplicated boot line add
	<tt>/debug /debugport=COM1 /baudrate=115200</tt>.		<br><tt>/debug /debugport=COM1 /baudrate=115200</tt>.
	<br>The baudrate and debugport must be identical to kernel mode configure of WinDbg.		<br>The baudrate and debugport must be identical to kernel mode configure of WinDbg.
	<br>If Windows7,Vista or up,you must use <tt>BCDedit</tt>(ref:http://technet.microsoft.com/en-us/library/cc709667%28WS.10%29.aspx and http://msdn.microsoft.com/en-us/library/ff542187.aspx ).		<br>If Windows7,Vista or up,you must use <tt>BCDedit</tt>(ref:http://technet.microsoft.com/en-us/library/cc709667%28WS.10%29.aspx and http://msdn.microsoft.com/en-us/library/ff542187.aspx ).
Line 142:		Line 142:

	* Using crash dump (kernel memory dump)with WinDbg		* Using crash dump (kernel memory dump)with WinDbg
			<pre style="color:red">
	TBD.		TBD.
			</pre>

	==Problems may be encountered==		==Problems may be encountered==

Caobingbu at 09:05, 10 November 2011

2011-11-10T09:05:44Z

← Older revision		Revision as of 05:05, 10 November 2011
Line 28:		Line 28:
	<br><tt><nowiki>c:\symbols\local_symbols;c:\driver\symbols;SRVc:\symbols\websymbolshttp://msdl.microsoft.com/download/symbols</nowiki></tt>		<br><tt><nowiki>c:\symbols\local_symbols;c:\driver\symbols;SRVc:\symbols\websymbolshttp://msdl.microsoft.com/download/symbols</nowiki></tt>

	~~====About the 3 different symbols====~~
	{\| border="1"		{\| border="1"
	\|'''symbol '''		\|'''symbol '''
Line 65:		Line 64:
	=Debug=		=Debug=
	When Host and target setup completely,restart the target virtual machine and select the DEBUG boot option in the boot menu.		When Host and target setup completely,restart the target virtual machine and select the DEBUG boot option in the boot menu.
			<br>Then WinDbg on host will try to connect to the windows guest(target) kernel to debug.
			<br>You can <tt>Ctrl+Break</tt> or use the <tt>Pause</tt> button to break the guest running and also you can do anything which the debug tool support.
	==About WinDbg==		==About WinDbg==
	WinDbg is a multi-purposed debugger for Microsoft Windows, distributed on the web by Microsoft. It can be used to debug user mode applications, drivers, and the operating system itself in kernel mode.		WinDbg is a multi-purposed debugger for Microsoft Windows, distributed on the web by Microsoft. It can be used to debug user mode applications, drivers, and the operating system itself in kernel mode.
	~~<br>Then WinDbg on host will try to connect to the windows guest(target) kernel to debug.~~
	~~<br>You can <tt>Ctrl+Break</tt> or use the <tt>Pause</tt> button to break the guest running and also you can do anything which the debug tool support.~~

	==Compile and build==		==Compile and build==

Caobingbu at 09:00, 10 November 2011

2011-11-10T09:00:42Z

← Older revision		Revision as of 05:00, 10 November 2011
Line 49:		Line 49:
	You can also add that into a *.bat file and create symbols automatically when every building.		You can also add that into a *.bat file and create symbols automatically when every building.

	====Run ~~Kernel Debug~~====		====Run WinDbg====
	Then <tt>File->Kernel Debug...</tt> or <tt>[Ctrl+k]</tt> select <tt>COM</tt> tab and set <tt>Baudrate</tt> to 115200 and set port to <tt>COM1</tt>,confirm and wait the target to connect.		Then <tt>File->Kernel Debug...</tt> or <tt>[Ctrl+k]</tt> select <tt>COM</tt> tab and set <tt>Baudrate</tt> to 115200 and set port to <tt>COM1</tt>,confirm and wait the target to connect.
	===Setting up the target VM===		===Setting up the target VM===