Where is the .exe file and where is the .pdb file? Show complete path
names; feel free to uniformly obfuscate anything that might reveal
proprietary information. Did you in any way modify the VS project
properties after creating it?
I regularly debug code in VS from a remapped server driver (i:, in my case)
and have never hit this problem. If you are hitting it, given that it is on
a disk managed by your driver, you probably need to see if you are doing all
the remappings to subdirectories correctly. I’d suggest trying filemon to
see what is being accessed.
joe
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@sivaller.no-ip.org
Sent: Sunday, October 03, 2010 5:47 AM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Problem with debugging information
Hi,
I’m on a virtual disk file system driver.
The driver letter is “n:” containing virtual file disk system managed by my
driver.
I can see the files from the explorer, and execute program from virtual
disk file system.
The filemapping works.
I tried and correct accordingly, create a new project Visual Studio “Hello
World” (console application) on my drive “N:” (my virtual disk file system)
is good.
The compiling and linking is OK, the program “Hello World” runs well on the
drive “n”:.
TroubleShooting:
When I run the “Hello World”'s program from my drive “n:”, Visual Studio
tells me it can not find the debugging information in the “Hello World”,
suddenly the breakpoint does not work .
Yet I good select Debug mode and not Release.
Do you have a solution?
Thank you
NTFSD is sponsored by OSR
For our schedule of debugging and file system seminars
(including our new fs mini-filter seminar) 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
–
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.