I am new to driver development and trying to learn it by debugging the
sample driver codes. Also, I am new to OSR online so kindly excuse me for
any unintentional mistake.
I was debugging driver on vmware with host OS and guest OS as win xp and it
was working fine but now when i try to debug it with host OS as win 7 64
bits Home premium and win xp(32 bits) as guest operating system windbg fails
to connect to xp.
Are you starting vmware & windbg using ‘Run as Administrator?’
mm
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of saurabh dhir
Sent: Saturday, December 18, 2010 4:43 AM
To: Kernel Debugging Interest List
Subject: [windbg] Problem while debugging driver on win 7
Hi,
I am new to driver development and trying to learn it by debugging the
sample driver codes. Also, I am new to OSR online so kindly excuse me for
any unintentional mistake.
I was debugging driver on vmware with host OS and guest OS as win xp and it
was working fine but now when i try to debug it with host OS as win 7 64
bits Home premium and win xp(32 bits) as guest operating system windbg fails
to connect to xp.
I learned to debug driver on vmware from the following link:
I am running x86 win xp vmimage(target machine) on top of x64 win 7(host
machine). I have modified the boot.ini of the target machine as follows:
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Microsoft Windows XP
Professional” /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Microsoft Windows XP
Professional Debug” /noexecute=optin /fastdetect /debug /debugport=com1
/baudrate=115200
and using the following command line to run windbg and connect to target
machine’s kernel:
cd C:\WinDDK\7600.16385.1\Debuggers
windbg -b -k com:pipe,port=\.\pipe\com1,resets=0
But despite doing all this I am unable to connect windbg of host machine to
connect to the kernel of target machine. I always get the folowing output
displayed on windbg:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Opened \.\pipe\com1
Waiting to reconnect…
**
This is troubling me since many days and i have reinstalled the winddk also
to verify the installation. Any suggestion will be of great help.
* PS: I am opening windbg and vmware both as administrators.*
Not only setup is done almost automaticlly, it much faster and remove the
COM port emulation bottle-neck.
Elad
On Sat, Dec 25, 2010 at 7:40 PM, saurabh dhir wrote:
> Hi, >> >> I am running x86 win xp vmimage(target machine) on top of x64 win 7(host >> machine). I have modified the boot.ini of the target machine as follows: >> >> [operating systems] >> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Microsoft Windows XP >> Professional” /noexecute=optin /fastdetect >> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Microsoft Windows XP >> Professional Debug” /noexecute=optin /fastdetect /debug /debugport=com1 >> /baudrate=115200 >> >> and using the following command line to run windbg and connect to target >> machine’s kernel: >> cd C:\WinDDK\7600.16385.1\Debuggers >> windbg -b -k com:pipe,port=\.\pipe\com1,resets=0 >> >> I have also made the necessary changes to the serial port settings as >> mentioned on this http://silverstr.ufies.org/lotr0/windbg-vmware.html >> URL. >> >> But despite doing all this I am unable to connect windbg of host machine >> to connect to the kernel of target machine. I always get the folowing output >> displayed on windbg: >> >> Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 >> Copyright (c) Microsoft Corporation. All rights reserved. >> >> Opened \.\pipe\com1 >> Waiting to reconnect… >> >> ** >> > This is troubling me since many days and i have reinstalled the winddk >> also to verify the installation. Any suggestion will be of great help. >> > > * PS: I am opening windbg and vmware both as administrators.* > >> Thanks, >> Saurabh >> > > — WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging > and other seminars visit: http://www.osr.com/seminars To unsubscribe, > visit the List Server section of OSR Online at > http://www.osronline.com/page.cfm?name=ListServer >
+1
On Dec 30, 2010 11:21 AM, “Elad Zucker” wrote: > I highly recommend you to use VirtualKD http://virtualkd.sysprogs.org/ if > you are debugging via VMWare or VirtualBox. > > Not only setup is done almost automaticlly, it much faster and remove the > COM port emulation bottle-neck. > > Elad > > > > On Sat, Dec 25, 2010 at 7:40 PM, saurabh dhir wrote: > >> Hi, >>> >>> I am running x86 win xp vmimage(target machine) on top of x64 win 7(host >>> machine). I have modified the boot.ini of the target machine as follows: >>> >>> [operating systems] >>> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Microsoft Windows XP >>> Professional” /noexecute=optin /fastdetect >>> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=“Microsoft Windows XP >>> Professional Debug” /noexecute=optin /fastdetect /debug /debugport=com1 >>> /baudrate=115200 >>> >>> and using the following command line to run windbg and connect to target >>> machine’s kernel: >>> cd C:\WinDDK\7600.16385.1\Debuggers >>> windbg -b -k com:pipe,port=\.\pipe\com1,resets=0 >>> >>> I have also made the necessary changes to the serial port settings as >>> mentioned on this http://silverstr.ufies.org/lotr0/windbg-vmware.html >>> URL. >>> >>> But despite doing all this I am unable to connect windbg of host machine >>> to connect to the kernel of target machine. I always get the folowing output >>> displayed on windbg: >>> >>> Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 >>> Copyright (c) Microsoft Corporation. All rights reserved. >>> >>> Opened \.\pipe\com1 >>> Waiting to reconnect… >>> >>> ** >>> >> This is troubling me since many days and i have reinstalled the winddk >>> also to verify the installation. Any suggestion will be of great help. >>> >> >> * PS: I am opening windbg and vmware both as administrators.* >> >>> Thanks, >>> Saurabh >>> >> >> — WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging >> and other seminars visit: http://www.osr.com/seminars To unsubscribe, >> visit the List Server section of OSR Online at >> http://www.osronline.com/page.cfm?name=ListServer >> > > — > WINDBG is sponsored by OSR > > For our schedule of WDF, WDM, debugging and other seminars visit: > http://www.osr.com/seminars > > To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer