Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results
Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.More Info on Driver Writing and Debugging
The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
Failed to connect Windbg to 2008R2 using named pipe
sachin_shinde
Member - All Emails Posts: 61
in WINDBG
Hi All,
I wanted to connect WinDBG for debugging, two systems (Debugee and Debugger) are VMs on ESXi 6.5 server, created named PIPE in on both systems. Followed all instructions ?https://communities.vmware.com/docs/DOC-15691?
Debugger System :Windows 10 and target Debugee: Windows Server 2008 R2, but I failed to connect WinDbg properly, showing message ?waiting to connect? for infinite time. Target Debuggee is blocked/Freezed but WinDbg
not able to proceed.
I have noticed one observation that, on creating named pipe on Target system(2008R2), didn?t find any port when checked in Device Manager, expecting port COM1 or COM2 to be created.
Checked with different pipe naming conventions ?pipe2k8? also ?\\.\pipe\pipe2k8?.
Any clue will be really helpful.
Thanks in advance.
~Sachin
I wanted to connect WinDBG for debugging, two systems (Debugee and Debugger) are VMs on ESXi 6.5 server, created named PIPE in on both systems. Followed all instructions ?https://communities.vmware.com/docs/DOC-15691?
Debugger System :Windows 10 and target Debugee: Windows Server 2008 R2, but I failed to connect WinDbg properly, showing message ?waiting to connect? for infinite time. Target Debuggee is blocked/Freezed but WinDbg
not able to proceed.
I have noticed one observation that, on creating named pipe on Target system(2008R2), didn?t find any port when checked in Device Manager, expecting port COM1 or COM2 to be created.
Checked with different pipe naming conventions ?pipe2k8? also ?\\.\pipe\pipe2k8?.
Any clue will be really helpful.
Thanks in advance.
~Sachin
| Upcoming OSR Seminars | ||
|---|---|---|
| OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead! | Kernel Debugging | 30 Mar 2020 | OSR Seminar Space |
| Developing Minifilters | 15 Jun 2020 | LIVE ONLINE |
| Writing WDF Drivers | 22 June 2020 | LIVE ONLINE |
| Internals & Software Drivers | 28 Sept 2020 | Dulles, VA |
Comments
Have you tried manually breaking with WinDbg on the debugger system
(Ctrl+Break)? Also, if you turn our debug protocol output with Ctrl+Alt+D do
you see anything?
-scott
OSR
@OSRDrivers
wrote in message news:[email protected]
I am able to connect two VMs bidirectionally using hyperTerminal
-scott
OSR
Got problem solved, CHECKed pipe and reconnect options, need to these options UNCHECK in WinDBG as per VMware esxi doc.