Inaccesible path

NTDEV
1

I try to follow how to debug in kernel_debuging_tuturial.doc, but i have a problem:
First, i build the sample of ioctl in computer target and i log on in computer target with administrator previlege. Then i copy the ioctl.sys and ioctlapp to directroy of computer target e:\temp and then i put command in windbg: .scrpath e:\temp . But it shows warning inaccesible path. And when i type ioctl in windbg directory it shows: ^ Syntax error in ‘ioctlapp’ Why was that?

2

The source code needs to be on the host computer, not the target.

Good luck,

mm

3

Thanks for the information. But, where should i put the code in the computer host? It is not so clear from the tutorial that i read.
And the symbol for the driver is not found by the computer host. Do i have to make the symbol can be found by the computer host?
?
Regards,
Sofian

— On Wed, 9/2/09, xxxxx@evitechnology.com wrote:

From: xxxxx@evitechnology.com
Subject: RE:[ntdev] Inaccesible path
To: “Windows System Software Devs Interest List”
Date: Wednesday, September 2, 2009, 11:31 AM

The source code needs to be on the host computer, not the target.

Good luck,

mm

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

4

This question should be on the windbg list. As it happens, your question there and this one are fundamentally the same, so please stop posting to this one.

mm

5

If you build the driver on the host system, it will contain a string indicating where the PDB is located. When you install it on the target system using a device manager install or .kdfiles, windbg will locate the pdb easily. Leave the source code in the same location where it was when the driver was compiled. You can move systems if the path names match on the build and host system, but I try and use one computer for both. If this is a released binary made on a ‘build system’ use a local symbol server and put all build symbols into the server as part of the build process.
“sahrizal sofian” wrote in message news:xxxxx@ntdev…
Thanks for the information. But, where should i put the code in the computer host? It is not so clear from the tutorial that i read.
And the symbol for the driver is not found by the computer host. Do i have to make the symbol can be found by the computer host?

Regards,
Sofian

— On Wed, 9/2/09, xxxxx@evitechnology.com wrote:

From: xxxxx@evitechnology.com
Subject: RE:[ntdev] Inaccesible path
To: “Windows System Software Devs Interest List”
Date: Wednesday, September 2, 2009, 11:31 AM

The source code needs to be on the host computer, not the target.

Good luck,

mm

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer