I was debugging fine using a VMWare Virtual machine. I stopped debugging and restarted the Virtual Machine and now I cannot get back into my debugging session?! I keep getting the following message;
“Could not start kernel debugging using com:pipe,port=\.\pipe\com_1 parameters, Win32 error 2” “The system cannot find the file specified”
Has anyone seen this error?
yes. I have found that if you shut down the VMWare Virtual Machine,
close the VMWare workstation, close Windbg, then open everything, all
is good again.
Sharon
sid.schipper@ga.com wrote:
I was debugging fine using a VMWare Virtual machine. I stopped debugging and restarted the Virtual Machine and now I cannot get back into my debugging session?! I keep getting the following message;
“Could not start kernel debugging using com:pipe,port=\.\pipe\com_1 parameters, Win32 error 2” “The system cannot find the file specified”
Has anyone seen this error?
You are currently subscribed to windbg as: xxxxx@cruzio.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Thank you all, but I figured out the problem on my own. When you restart the VM it doesn’t automatically connect to the serial port, you have to manually connect via the Devices menu.
OK, now I’m further along but things are still not good. I am trying to work through the example on page 31 of the fourth edition of thw Windows Internals book by Mark Russinovitch.
When I type in the command to kd, dt nt!_*, I get no response at all. If I then try to type in the other command on that page, namely, ds nt!kinterrupt, I get the following message;
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_kinterrupt ***
*** ***
*************************************************************************
Symbol nt!_kinterrupt not found.
I have my symbol path set up as specified in the book, namely, pointing to srv*C:\Symbols*http://msdl.microsoft.com/download/symbols.
Can anyone tell me what I am doing wrong?
Try verifying via .sympath and .symfix … does your guest have access
to the network (i.e. symbol server)?
sid.schipper@ga.com wrote:
OK, now I’m further along but things are still not good. I am trying to work through the example on page 31 of the fourth edition of thw Windows Internals book by Mark Russinovitch.
When I type in the command to kd, dt nt!_*, I get no response at all. If I then try to type in the other command on that page, namely, ds nt!kinterrupt, I get the following message;
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_kinterrupt ***
*** ***
*************************************************************************
Symbol nt!_kinterrupt not found.I have my symbol path set up as specified in the book, namely, pointing to srv*C:\Symbols*http://msdl.microsoft.com/download/symbols.
Can anyone tell me what I am doing wrong?
type .reload
Kenny Speer wrote:
Try verifying via .sympath and .symfix … does your guest have access
to the network (i.e. symbol server)?sid.schipper@ga.com wrote:
> OK, now I’m further along but things are still not good. I am trying
> to work through the example on page 31 of the fourth edition of thw
> Windows Internals book by Mark Russinovitch.
> When I type in the command to kd, dt nt!_*, I get no response at all.
> If I then try to type in the other command on that page, namely, ds
> nt!kinterrupt, I get the following message;
>
> *************************************************************************
>
> ***
> ***
> ***
> ***
> *** Your debugger is not using the correct symbols
> ***
> ***
> ***
> *** In order for this command to work properly, your symbol path
> ***
> *** must point to .pdb files that have full type information.
> ***
> ***
> ***
> *** Certain .pdb files (such as the public OS symbols) do not
> ***
> *** contain the required information. Contact the group that
> ***
> *** provided you with these symbols if you need this command to
> ***
> *** work.
> ***
> ***
> ***
> *** Type referenced: nt!_kinterrupt
> ***
> ***
> ***
> *************************************************************************
>
> Symbol nt!_kinterrupt not found.
>
> I have my symbol path set up as specified in the book, namely,
> pointing to srv*C:\Symbols*http://msdl.microsoft.com/download/symbols.
>
> Can anyone tell me what I am doing wrong?
You are currently subscribed to windbg as: xxxxx@cruzio.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
If I understand the situation correctly, ‘ds nt!kinterrupt’ doesn’t make
any sense. That is, nt!kinterrupt is a type, so I don’t see what ‘ds’
has to do with it. I think you might mean ‘dt.’ Also, be aware, that
it is possible, though not by default, that your symbol options could be
set to case sensitive, which would cause ‘kinterrupt’ to fail to match,
as it is ‘KINTERRUPT.’
Symbols in a nutshell:
.symopt+0x80000000
.sympath srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
.reload -f -n
lml
Minimally, you must have pdb symbols (not export symbols) for
nt(ntoskrnl). If things are working correctly, you should have them for
most modules, but not all, and probably none for anything that isn’t
provided by Microsoft or you.
Good luck,
mm
Kenny Speer wrote:
Try verifying via .sympath and .symfix … does your guest have access
to the network (i.e. symbol server)?sid.schipper@ga.com wrote:
> OK, now I’m further along but things are still not good. I am trying
> to work through the example on page 31 of the fourth edition of thw
> Windows Internals book by Mark Russinovitch.
> When I type in the command to kd, dt nt!_*, I get no response at all.
> If I then try to type in the other command on that page, namely, ds
> nt!kinterrupt, I get the following message;
>
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!_kinterrupt ***
> *** ***
> *************************************************************************
> Symbol nt!_kinterrupt not found.
>
> I have my symbol path set up as specified in the book, namely,
> pointing to srv*C:\Symbols*http://msdl.microsoft.com/download/symbols.
>
> Can anyone tell me what I am doing wrong?
Check that reconnect at power on is set in the serial port settings.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-316694-
xxxxx@lists.osr.com] On Behalf Of sid.schipper@ga.com
Sent: Thursday, March 06, 2008 11:09 AM
To: Kernel Debugging Interest List
Subject: RE:[windbg] Debugging Using a Virtual MachineThank you all, but I figured out the problem on my own. When you restart
the VM it doesn’t automatically connect to the serial port, you have to
manually connect via the Devices menu.
You are currently subscribed to windbg as: xxxxx@berktool.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
OK, I got past all those problems and everything is Hunky-Dory now. Thanks for all tghe feed back and help.