I just upgraded my OS from XP SP3 to Windows 7. What I did until now was to
debug an application using COM connection (a pipe with name \.\com_1) that
was hosted on a virtual machine (VMware 5.5).
When the OS on my machine was XP, everything went smoothly, I had windbg
6.8.4. When I upgraded to W7 (on the real machine, the VM debugged OS is
still XP), I installed the latest version of Windbg. The problem is that
when I use the File -> Kernel Dubg … (Ctrl+K) option, my Command window
(Alt+1) dissapears, and I can NOT issue commands and worst, I can’t see
debug messages issued by calls to OutputDebugString, DbgPrint, etc. I set up
the flags (http://www.osronline.com/article.cfm?article=295), I even
installed older versions of WinDbg, and I even tried runing in compatibility
mode with older systems, but the result was the same: the Command window
(Alt + 1) is invisible as soon as I make a kernel connection to the Virtual
machine. Is very frustrating because I can not issue command or see the
result or app trace messages.
You can try undocking all of the windows and seeing if it appears again
(Window->Undock all). I’ve seen people manage to dock the command window
someplace hidden in class though I’ve never done it myself (and I use the
same config as you).
If that doesn’t work, try deleting the HKCU\Software\Microsoft\Windbg key to
entirely wipe out your workspaces and then try again.
“Andrei Muraru” wrote in message news:xxxxx@windbg… Hello guys,
I just upgraded my OS from XP SP3 to Windows 7. What I did until now was to debug an application using COM connection (a pipe with name \.\com_1) that was hosted on a virtual machine (VMware 5.5). When the OS on my machine was XP, everything went smoothly, I had windbg 6.8.4. When I upgraded to W7 (on the real machine, the VM debugged OS is still XP), I installed the latest version of Windbg. The problem is that when I use the File -> Kernel Dubg … (Ctrl+K) option, my Command window (Alt+1) dissapears, and I can NOT issue commands and worst, I can’t see debug messages issued by calls to OutputDebugString, DbgPrint, etc. I set up the flags (http://www.osronline.com/article.cfm?article=295), I even installed older versions of WinDbg, and I even tried runing in compatibility mode with older systems, but the result was the same: the Command window (Alt + 1) is invisible as soon as I make a kernel connection to the Virtual machine. Is very frustrating because I can not issue command or see the result or app trace messages.
I managed to make it work. I noticed that if I start Windbg without
parameters (I usually start with the command line that enables Kernel
connection), the Commands window is visible. So I saved a workspace that I
loaded after the kernel connection and voila … everything was fixed.
Nonetheles, there is a bug in Windbg which should be fixed.
Thanks,
Andrei M.
On Tue, Jun 8, 2010 at 5:03 PM, Scott Noone wrote:
> You can try undocking all of the windows and seeing if it appears again > (Window->Undock all). I’ve seen people manage to dock the command window > someplace hidden in class though I’ve never done it myself (and I use the > same config as you). > > If that doesn’t work, try deleting the HKCU\Software\Microsoft\Windbg key > to entirely wipe out your workspaces and then try again. > > -scott > > – > Scott Noone > Consulting Associate > OSR Open Systems Resources, Inc. > http://www.osronline.com > > > “Andrei Muraru” wrote in message news:xxxxx@windbg. > … > > Hello guys, > > > I just upgraded my OS from XP SP3 to Windows 7. What I did until now was to > debug an application using COM connection (a pipe with name \.\com_1) that > was hosted on a virtual machine (VMware 5.5). > When the OS on my machine was XP, everything went smoothly, I had windbg > 6.8.4. When I upgraded to W7 (on the real machine, the VM debugged OS is > still XP), I installed the latest version of Windbg. The problem is that > when I use the File -> Kernel Dubg … (Ctrl+K) option, my Command window > (Alt+1) dissapears, and I can NOT issue commands and worst, I can’t see > debug messages issued by calls to OutputDebugString, DbgPrint, etc. I set up > the flags (http://www.osronline.com/article.cfm?article=295), I even > installed older versions of WinDbg, and I even tried runing in compatibility > mode with older systems, but the result was the same: the Command window > (Alt + 1) is invisible as soon as I make a kernel connection to the Virtual > machine. Is very frustrating because I can not issue command or see the > result or app trace messages. > > > Any suggestion would be appreciated. > > > Thanks, > Andrei > > — > 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 >
What you’re doing is just creating a new workspace.
Good morning,
mm
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Andrei Muraru
Sent: Thursday, June 10, 2010 3:23 AM
To: Kernel Debugging Interest List
Subject: Re: [windbg] Windbg - command window is invisible on W7
I managed to make it work. I noticed that if I start Windbg without parameters (I usually start with the command line that enables Kernel connection), the Commands window is visible. So I saved a workspace that I loaded after the kernel connection and voila … everything was fixed. Nonetheles, there is a bug in Windbg which should be fixed.
Thanks,
Andrei M.
On Tue, Jun 8, 2010 at 5:03 PM, Scott Noone wrote:
You can try undocking all of the windows and seeing if it appears again (Window->Undock all). I’ve seen people manage to dock the command window someplace hidden in class though I’ve never done it myself (and I use the same config as you).
If that doesn’t work, try deleting the HKCU\Software\Microsoft\Windbg key to entirely wipe out your workspaces and then try again.
“Andrei Muraru” wrote in message news:xxxxx@windbg…
Hello guys,
I just upgraded my OS from XP SP3 to Windows 7. What I did until now was to debug an application using COM connection (a pipe with name \.\com_1 <file:> ) that was hosted on a virtual machine (VMware 5.5). When the OS on my machine was XP, everything went smoothly, I had windbg 6.8.4. When I upgraded to W7 (on the real machine, the VM debugged OS is still XP), I installed the latest version of Windbg. The problem is that when I use the File -> Kernel Dubg … (Ctrl+K) option, my Command window (Alt+1) dissapears, and I can NOT issue commands and worst, I can’t see debug messages issued by calls to OutputDebugString, DbgPrint, etc. I set up the flags (http://www.osronline.com/article.cfm?article=295), I even installed older versions of WinDbg, and I even tried runing in compatibility mode with older systems, but the result was the same: the Command window (Alt + 1) is invisible as soon as I make a kernel connection to the Virtual machine. Is very frustrating because I can not issue command or see the result or app trace messages.