I have a bug in my filesystem driver that I cannot trace.
I can view the root very well (f:).
But, if in Explorer or cmd I try switching to any lower level directory, 9 times out of 10 the app crashes, usually with a message going : The instruction at referenced memory at . The memory could not be “read” (someitme it says “written”). Sometimes the debugger mentions something about a heap corruption at the same time.
In cmd, while in f:, I can however type something like “dir dir1”, and it will correctly display the listing of dir1 without any problems. But “cd dir1” will cause cmd to crash. Logically speaking, both commands should be similar and should generate similar IRPs (though obviously in a different sequence and number).
Any advice on what to look out for? My driver itself never crashes/BSODs, but explorer/word/cmd all do.
-----------------------------------------------------------
Sign up and get your 30GB webmail at www.30gigs.com now!
build both your driver and user app with prefast if you haven’t tried
that yet (see if that can sniff out the bug).
Without a crash dump, I don’t think you’ll get much help, no one can
guess what is happening inside your code.
use the !analyze -v command to get the dump, and post that.
m
xxxxx@30gigs.com wrote:
I have a bug in my filesystem driver that I cannot trace.
I can view the root very well (f:).
But, if in Explorer or cmd I try switching to any lower level
directory, 9 times out of 10 the app crashes, usually with a message
going : The instruction at referenced memory at . The memory could not
be “read” (someitme it says “written”). Sometimes the debugger
mentions something about a heap corruption at the same time.
In cmd, while in f:, I can however type something like “dir dir1”, and
it will correctly display the listing of dir1 without any problems.
But “cd dir1” will cause cmd to crash. Logically speaking, both
commands should be similar and should generate similar IRPs (though
obviously in a different sequence and number).
Any advice on what to look out for? My driver itself never
crashes/BSODs, but explorer/word/cmd all do.
Hi…! Get this Exclusive Offer From 30gigs.com. Free Ipod Nano! Click
Here.
http:
> Don’t have 30gigs email account yet? Sign up and get your 30GB Webmail
> http:account
> Now! — Questions? First check the IFS FAQ at
> https://www.osronline.com/article.cfm?id=17 You are currently
> subscribed to ntfsd as: unknown lmsubst tag argument: ‘’ To
> unsubscribe send a blank email to xxxxx@lists.osr.com
></http:></http:>
I’d guess you are overwriting the application’s memory. You’ll need to
check your buffer handling code carefully.
Regards,
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.