Remote debugging steps ?

WINDBG
1

Hi All,

Could someone point me to a doc stating steps to do the remote
debugging over ip.

I’ve seen help of the winbag, but I was thinking along this -

At remote site what are the steps to take to start
crash-dump analysis over IP ?

If I want to do live kernel debugging remotely, how do we
configure, and how many
machines we need on the remote site ( may be 2 there ).

thanx
prokash

2

Could someone point me to a doc stating steps to do the remote
debugging over ip.
Have you looked at the debugger docs?

If I want to do live kernel debugging remotely, how do we
configure, and how many
machines we need on the remote site ( may be 2 there ).

You will need 3 machines total:
The machine being debugged
The machine attached to the debugee via
serial/1394. Run “windbg -server blahblahblah…” there. This is the
debugger machine.
The (remote) machine where you run “windbg
-remote blahblahblah…” to connect to the debugger machine.

Spend a few minutes and play with it on a couple of machines you
have in your office or whatever. You can even do it all on the same
machine (well if you remote out a user mode debugging session or dump
debugging session).

Doing it over the internet works the same. However you may have
issues with NAT, proxies, firewalls and such. But these are things that
any app communicating via TCP/IP will have and is not a debugger issue.
As such there are tons of resources on the web to tell you have to deal
with such things.

-----Original Message-----
From: Prokash Sinha [mailto:xxxxx@zonelabs.com]
Sent: Wednesday, April 24, 2002 10:49 AM
To: Kernel Debugging Interest List
Subject: [windbg] Remote debugging steps ?

Hi All,

Could someone point me to a doc stating steps to do the remote
debugging over ip.

I’ve seen help of the winbag, but I was thinking along this -

At remote site what are the steps to take to start
crash-dump analysis over IP ?

If I want to do live kernel debugging remotely, how do
we configure, and how many
machines we need on the remote site ( may be 2 there ).

thanx
prokash

You are currently subscribed to windbg as: xxxxx@microsoft.com To
unsubscribe send a blank email to %%email.unsub%%

3

Thanx
-prokash

-----Original Message-----
From: Nathan Nesbit [mailto:xxxxx@windows.microsoft.com]
Sent: Wednesday, April 24, 2002 11:17 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Remote debugging steps ?

Could someone point me to a doc stating steps to do the remote
debugging over ip.
Have you looked at the debugger docs?

If I want to do live kernel debugging remotely, how do we
configure, and how many
machines we need on the remote site ( may be 2 there ).

You will need 3 machines total:
The machine being debugged
The machine attached to the debugee via
serial/1394. Run “windbg -server blahblahblah…” there. This is the
debugger machine.
The (remote) machine where you run “windbg
-remote blahblahblah…” to connect to the debugger machine.

Spend a few minutes and play with it on a couple of machines you
have in your office or whatever. You can even do it all on the same
machine (well if you remote out a user mode debugging session or dump
debugging session).

Doing it over the internet works the same. However you may have
issues with NAT, proxies, firewalls and such. But these are things that
any app communicating via TCP/IP will have and is not a debugger issue.
As such there are tons of resources on the web to tell you have to deal
with such things.

-----Original Message-----
From: Prokash Sinha [mailto:xxxxx@zonelabs.com]
Sent: Wednesday, April 24, 2002 10:49 AM
To: Kernel Debugging Interest List
Subject: [windbg] Remote debugging steps ?

Hi All,

Could someone point me to a doc stating steps to do the remote
debugging over ip.

I’ve seen help of the winbag, but I was thinking along this -

At remote site what are the steps to take to start
crash-dump analysis over IP ?

If I want to do live kernel debugging remotely, how do
we configure, and how many
machines we need on the remote site ( may be 2 there ).

thanx
prokash

You are currently subscribed to windbg as: xxxxx@microsoft.com To
unsubscribe send a blank email to %%email.unsub%%

You are currently subscribed to windbg as: xxxxx@zonelabs.com
To unsubscribe send a blank email to %%email.unsub%%