Kernel remote debugging

NTFSD
1

Hi everybody, I am trying to remote debug a driver. I have tried to followed the steps given by Rajeev Nagar’s book.

The steps are these :
1: Install free or checked version of WNT on the target machine. I installed W2K Advanced Server (free).
2: Install a free version of WNT on the host machine. I installed W2K Pro (free too).
3: Install SDK on the host. I had already done it. I compiled the driver on the host machine.
4: Copy the target system’s debug symbol files to the host machine. I don’t have them. Is it necessary?
5: Modify the boot.ini on the taget. OK, I did it. (/DEBUG /DEBUGPORT = COM2 /BAUDRATE=57600)
6: Configure the WinDbg application on the host. Ok, same parameters as targets. I also set the symbols folder.
7: Copy symbolic information (dbg file) or the binary to the symbols folder. I didn’t see any dbg file, so I copied the cheched version of the driver.
8: Ensure you have the sources files on the host. That’s ok I compile on the host machine.
9: Start WinDbg. Ok too.
10: Boot the target. Ok, restart.

So, I set a source breakpoint with the DbgBreakPoint function and the systems freezes when it gets to this breakpoint but I don’t get control of it on the host. Can I debug with different OS? Are the debug symbols files necesary?

2

Say

x yourdriver!*

Is the output correct?

Then say

u SomeFunctionInYourDriver

Is the prolog correct?

Max

----- Original Message -----
From: Ratmil Torres
To: File Systems Developers
Sent: Saturday, September 28, 2002 4:07 AM
Subject: [ntfsd] Kernel remote debugging

Hi everybody, I am trying to remote debug a driver. I have tried to followed the steps given by Rajeev Nagar’s book.

The steps are these :
1: Install free or checked version of WNT on the target machine. I installed W2K Advanced Server (free).
2: Install a free version of WNT on the host machine. I installed W2K Pro (free too).
3: Install SDK on the host. I had already done it. I compiled the driver on the host machine.
4: Copy the target system’s debug symbol files to the host machine. I don’t have them. Is it necessary?
5: Modify the boot.ini on the taget. OK, I did it. (/DEBUG /DEBUGPORT = COM2 /BAUDRATE=57600)
6: Configure the WinDbg application on the host. Ok, same parameters as targets. I also set the symbols folder.
7: Copy symbolic information (dbg file) or the binary to the symbols folder. I didn’t see any dbg file, so I copied the cheched version of the driver.
8: Ensure you have the sources files on the host. That’s ok I compile on the host machine.
9: Start WinDbg. Ok too.
10: Boot the target. Ok, restart.

So, I set a source breakpoint with the DbgBreakPoint function and the systems freezes when it gets to this breakpoint but I don’t get control of it on the host. Can I debug with different OS? Are the debug symbols files necesary?

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

3

What version of the debugger are you using? If it isn’t version 6, download
the current version from http://www.microsoft.com/ddk/debugging
http: .

Regards,

Tony

Tony Mason

Consulting Partner

OSR Open Systems Resources, Inc.

http://www.osr.com

-----Original Message-----
From: Ratmil Torres [mailto:xxxxx@seg.inf.cu]
Sent: Friday, September 27, 2002 8:08 PM
To: File Systems Developers
Subject: [ntfsd] Kernel remote debugging

Hi everybody, I am trying to remote debug a driver. I have tried to followed
the steps given by Rajeev Nagar’s book.

The steps are these :

1: Install free or checked version of WNT on the target machine. I installed
W2K Advanced Server (free).

2: Install a free version of WNT on the host machine. I installed W2K Pro
(free too).

3: Install SDK on the host. I had already done it. I compiled the driver on
the host machine.

4: Copy the target system’s debug symbol files to the host machine. I don’t
have them. Is it necessary?

5: Modify the boot.ini on the taget. OK, I did it. (/DEBUG /DEBUGPORT = COM2
/BAUDRATE=57600)

6: Configure the WinDbg application on the host. Ok, same parameters as
targets. I also set the symbols folder.

7: Copy symbolic information (dbg file) or the binary to the symbols folder.
I didn’t see any dbg file, so I copied the cheched version of the driver.

8: Ensure you have the sources files on the host. That’s ok I compile on the
host machine.

9: Start WinDbg. Ok too.

10: Boot the target. Ok, restart.

So, I set a source breakpoint with the DbgBreakPoint function and the
systems freezes when it gets to this breakpoint but I don’t get control of
it on the host. Can I debug with different OS? Are the debug symbols files
necesary?

—
You are currently subscribed to ntfsd as: xxxxx@osr.com
To unsubscribe send a blank email to %%email.unsub%%</http:>