Remote kernel debugging?

Is it possible to kernel debug via a TCP connection? I’m thinking, two
machines wired with a COM cable; one is the debuggee proper, the other is
sort of a “server”. I would TCP into the “server” from a third machine and
do the kernel debugging.

By chance, is this what the “Connect to Remote Stub” command in Windbg is
for? Unfortunately it’s not described in the documentation or on the net.

Thanks.

Yes you can do this, look under the “Remote Debugging” section of the
documentation (under “Debuggers”).


Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
http://www.windrvr.com
Remove StopSpam from the email to reply

“Alexandru Pojoga” wrote in message
news:xxxxx@windbg…
> Is it possible to kernel debug via a TCP connection? I’m thinking, two
> machines wired with a COM cable; one is the debuggee proper, the other is
> sort of a “server”. I would TCP into the “server” from a third machine
> and
> do the kernel debugging.
>
> By chance, is this what the “Connect to Remote Stub” command in Windbg is
> for? Unfortunately it’s not described in the documentation or on the net.
>
> Thanks.
>

Yes. You can use -server with a kd.exe running with the serial connection or kdbgsrv directly with the serial connection. I would tend to use -server unless you are on a very high bandwidth / low latency link, in which case you might consider kdbgsrv.

Take a look at this post series for details and examples on both of those methods: < http://www.nynaeve.net/?p=38 >

Ken Johnson (Skywing)
Windows SDK MVP
http://www.nynaeve.net
“Alexandru Pojoga” wrote in message news:xxxxx@windbg…
Is it possible to kernel debug via a TCP connection? I’m thinking, two machines wired with a COM cable; one is the debuggee proper, the other is sort of a “server”. I would TCP into the “server” from a third machine and do the kernel debugging.

By chance, is this what the “Connect to Remote Stub” command in Windbg is for? Unfortunately it’s not described in the documentation or on the net.

Thanks.