Remote debugging with WinDbg over 1394 cable
I really don't get it. How can I make this work?
On the host computer I opened a WinDbg with Administrator rights, went to File | Kernel Debug and in the 1394 tab I entered channel 12 (MSDN tells me I can pick whatever I want from 0 to 64), I click OK and WinDbg tells me that it is waiting to reconnect.
So far, so good.
On the target machine what should I do?
I understand little to nothing from http://msdn.microsoft.com/en-us/library/windows/hardware/ff537819(v=vs.85).aspx (Activating a Debugger Client)
What should I enter in the Connection String text box? To me it seems that nothing from there has anything to do with 1394 and File | Connect to Remote Stub does nothing.
Now, if I do it like the paragraph Using The Command Line paragraph from this article http://msdn.microsoft.com/en-us/library/windows/hardware/hh451173(v=vs.85).aspx I get the following message
message, but then everything else (like breaking in as explained here http://msdn.microsoft.com/en-us/library/windows/hardware/dn745912(v=vs.85).aspx ) ends with
I thought that I'm not really connected, but if I close WinDbg on the target computer, the host one warns me that the client has disconnected, and if I close the host, the client informs me that this debugging session will end because the host has disconnected.
All I want is some clear example.
Also, http://msdn.microsoft.com/en-us/library/windows/hardware/ff556866(v=vs.85).aspx does nothing.
off-topic side question: how do I format URLs on this forum? [url=""][/url] failed me.
On the host computer I opened a WinDbg with Administrator rights, went to File | Kernel Debug and in the 1394 tab I entered channel 12 (MSDN tells me I can pick whatever I want from 0 to 64), I click OK and WinDbg tells me that it is waiting to reconnect.
So far, so good.
On the target machine what should I do?
I understand little to nothing from http://msdn.microsoft.com/en-us/library/windows/hardware/ff537819(v=vs.85).aspx (Activating a Debugger Client)
What should I enter in the Connection String text box? To me it seems that nothing from there has anything to do with 1394 and File | Connect to Remote Stub does nothing.
Now, if I do it like the paragraph Using The Command Line paragraph from this article http://msdn.microsoft.com/en-us/library/windows/hardware/hh451173(v=vs.85).aspx I get the following message
connected at Mon Aug 18 01:53:44 2014 |
Wrote 0 of 1 bytes of the breakin packet. Failed to write breakin packet to target. Win32 error 0n2 WARNING: The HOST cannot communicate with the TARGET! |
I thought that I'm not really connected, but if I close WinDbg on the target computer, the host one warns me that the client has disconnected, and if I close the host, the client informs me that this debugging session will end because the host has disconnected.
All I want is some clear example.
Also, http://msdn.microsoft.com/en-us/library/windows/hardware/ff556866(v=vs.85).aspx does nothing.
off-topic side question: how do I format URLs on this forum? [url=""][/url] failed me.
Last edited on
Topic archived. No new replies allowed.