I'm trying to get WinDbg debugging over the network to work, but it always loses connections after I break into the debugger (Debug->Break), and then try to start it again (Debug->Go). However, if I never break into the debugger, it looks like the connection is stable for an 'N' period of time. I can even see debug print statements in WinDbg as I use the target system during this grace period. Moreover, It seems like the connection is good while in debug break, because I can gather information from the target system. I use '!ustr srv!SrvComputerName' to get the target computer name, and it returns the correct name. Any help would be much appreciated.
Setting up the systems: I followed instructions from MSDN website to setup my target and host systems.
Debugging: Below are my attempts to resolve this issue.
Observation:
System Info: The host system is running Windows 8.1 Pro. The target system is running a Windows 8.1 Enterprise Evaluation (8GB of RAM).
WinDbg print out:
At this point WinDbg is no longer responsive, and continue sending data packets. The target system is also non-responsive.
Community♦
tchau.devtchau.dev
4 Answers
I finally solved this problem by switching the host system. In the beginning, I thought the target system was the problem, because MSDN only put the NIC debug requirement on the target system. It appears that there might be requirements placed the host system as well.
New host system: Desktop (Identical to target system)
Previous host system: Laptop
NOTE: I don't really know the root cause. Both NICs are on the Supported Ethernet NICs list, I used the same WinDbg version that came with the WDK, and all systems are on the same switch.
tchau.devtchau.dev
I had the similar problem and solved it by using USB to Ethernet adapter on the host machine instead of in built NIC card.
Girish BRGirish BR
I found a simpler solution that worked for me in VMware, The problem is in vmware - the NAT connection has a 30 seconds timeout.This value is configurable.Go to edit -> virtual network editor -> change settings (uac prompt) -> select NAT in the list -> NAT settings -> UDP timeout.The max value is 32767, the default (for me) was 30 seconds.It completely solved my problem.
shaked cohenshaked cohen
I also met this issue, and found that when I try to force shutdown VMWare OS, the windbg connection seems recover before VMWare OS is actually closed. After several tries, I found a weird solution:
When the windbg connection between host and VMWare guest lost, try to click 'shutdown VMWare Guest', but DO NOT really confirm. And you may found that the windbg connection recovers! Then, cancel the shutdown.
It's very strange, seems VMWare itself blocked the network debugging connection lost. Soft4boost video capture full crack free. But at least it's a workaround worth trying.
Another workaround I tried, which sometimes work, is killing windbg in task manager, and re-run windbg and reconnect to VMWare guest. And may need wait seconds to minutes until it reconnects.
btw, my ethernet card is Intel Ethernet Connection I218-V.
IvelliosIvellios
Not the answer you're looking for? Browse other questions tagged debuggingwindbgkernel-mode or ask your own question.
I am trying to do Windows kernel debugging so I have set up two machines for this purpose:
Both HOST and TARGET runs Windows 7 32 bit and both have Windows Driver Kit 8.0 installed. I did the following steps:
On TARGET I've enabled kernel debugging with following commands:
Then I've started HOST and did the following steps:
After this my windbg command window on HOST looks like this:
Then I've restarted TARGET and choose 'Windows 7 with debug' from the boot menu.
After this my windbg command window on HOST looks like this:
But instead of prompt where usually commands are typed I get:
Debuggee not connected. The TARGET system started as usual and I was able to use it.
Few things I've noticed:
What i am doing wrong?
PS: Both machines are virtual guests on XEN.PPS: Connection is 100% working, tested on kernel with no debugging enabled and with putty
EDIT:
Title changed.
According to this article My Kernel Debugger Won't Connect it is OK that COM1 is missing:
By checking Device Manager I was able to confirm that there was a problem with the configuration of the OS running in the VM. The bcdedit settings were configured to use COM1, and this should make COM1 unavailable in the OS, however, COM1 was present in device manager. For some reason the debugger was not capturing COM1 on boot as it was configured to.
I've also checked the settings described in mentioned article but they seems to be OK also:
EDIT2
Based on this SO answer I've tried issue
kd -kl command. I suppose it should be issued only on target but to be sure I've tried both machines. You can see that there is an error regarding symbols but I think debugging should be working without them also.
HOST:
TARGET:
There are also some recommendations about setting printer sharing etc. are they worth trying?
Community♦
Wakan TankaWakan Tanka
2,63655 gold badges3434 silver badges7676 bronze badges
2 Answers
It looks like you got the debugger attached to the target. (1) Ignore WinDbg status message. The best way to see if you're connected to the target is to try a few commands. (2) When I debug a virtual machine, the serial port that I'm using also goes missing, but it looks like you figured that out (good job).
In order to issue commands you need to break into the kernel. Click 'Debug->Break' and try the following commands:
That should give you the target system computer name.
If you want to learn more about kernel debugging, I would check out TheSourceLens on YouTube. As for literature, I can't recommend any books, because most information I find are online. However, I would recommend checking out OSR Online. Happy debugging.
tchau.devtchau.dev
You can try Bellavista.exe to create a new debug entry and look for the differences.
zapadorzapador
40711 gold badge88 silver badges1717 bronze badges
Not the answer you're looking for? Browse other questions tagged windowsdebuggingkernelwindbg or ask your own question.
I have the following configuration:
Host OS: Windows 7 SP1Guest OS: Windows XP SP3 Pro
Guest OS is running inside VMWare Workstation version 7
I have configured a virtual serial port on the VM of type 'output named pipe' and the following name:
I have also added the appropriate options to the boot.ini file on Win XP SP3 Pro image to allow for debugging (/debugport=com1 baudrate=115200)
in windbg, I configure the Kernel Debug option by going to:
File->Kernel Debug
and selecting the COM tab and configuring as follows:
Giving port name as:
and checking the Pipe box.
I boot up the Windows XP SP3 VM and select the second entry which has debug mode enabled. Right after I do this, I click on Ok inside the Windbg to start the kernel debugging session.
But even then it remains stuck at the following message:
Opened .pipewhateverWaiting to reconnect..
It says 'Debuggee not connected' and stays at that message even after Virtual Machine boots up completely. The status of the Virtual Serial port in the VmWare also shows as Connected.
I have checked the network connections.
The VM has the Network Adapter in the Bridged Mode and I am able to ping the Guest OS and Host OS from each other successfully.
Windows media player live streaming. Listening to Internet radio using Windows Media Player 12 gives you a great way to discover music by tuning into real FM stations that broadcast. Lifewire How to Use Streaming Windows Internet Radio. Search the site GO. Software & Apps. Video & Audio Browsers & Internet Backup & Utilities. Lifewire is part of the Dotdash. Apr 05, 2019 After your system is restored to the earlier configuration, check to see whether Windows Media Player runs correctly again. For advanced video features like 4K, you might also want to try Microsoft Movies & TV. To download this for free from Microsoft Store, go to Movies & TV and select Get. H96 max X2 Android 8.1 TV Box, 4GB RAM 32GB ROM Amlogic Quad core Support WiFi 2.4G+5G/4K/3D Smart TV Box Streaming Media Player. 1-24 of over 1,000 results for Electronics: Television & Video: Streaming Media Players. Fire TV Stick with. Nov 25, 2013 This will show you how to turn media streaming using Windows Media Player on or off for all users in Windows 7. To Turn On Media Streaming from Windows Media Player 12A) Open Windows Media Player (wmplayer.exe). How can I configure the player when I start a streamed video/TV, to start automatically, not to click again the PLAY.
Neon FlashNeon Flash
1,31688 gold badges3939 silver badges7070 bronze badges
4 Answers
Your problem is likely to be that WinDbg isn't breaking on connect, so it's connected but it doesn't say so, and you think it's not working.
I had better luck running WinDbg from the command line with a -b, though I notice this option might have been removed in the later builds. I've tested with 6.12.0002.633 x86.
(From here.)
Nick WestgateNick Westgate
Using Usb For Debugging Waiting To Reconnect Windows 10
2,01711 gold badge2222 silver badges2929 bronze badges
I have had the same problem, and after changing the port at your windows guest (the one at the vmware) you should be connect. In my case the port at the Hanan N.Hanan N.
boot.ini file was com1 and i have changed it to com2 .
79322 gold badges1616 silver badges3535 bronze badges
jcopenhajcopenha
3,81711 gold badge1212 silver badges1414 bronze badges
It could also be your VMWare serial port configuration. Config should be:
Using Usb For Debugging Waiting To Reconnect Mac
Use named pipe: .pipewhateverThis end is the server.The other end is an application.
Yield CPU on poll should be checked.
More info here:http://www.vmware.com/support/ws5/doc/ws_devices_serial_advanced_example_debugging.html
AlnoorAlnoor
Not the answer you're looking for? Browse other questions tagged windbg or ask your own question.Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |