Hi all,
i have a filesytem filter driver that boots the machine or sometimes gives
a blue screen. This happens after a few hours on activating the driver. How
should I debug the driver?
I am thinking of installing a checked build version of NT and building the
checked version of the driver. Will that be of any help? Any suggessions
are welcome.
Regards.
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Hi Vikrant
Ya its the only prefered and zero-cost way to trace problem in
kernel-development :). Even if it success you must trace and assure
functionality of your development in debug setup then only finalize and
introduce solution.
And not forgot to install check buid of SP, if you need that.
Happy debugging.
– Sumit
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of xxxxx@yahoo.com
i have a filesytem filter driver that boots the machine or sometimes gives
a blue screen. This happens after a few hours on activating the driver. How
should I debug the driver?
I am thinking of installing a checked build version of NT and building the
checked version of the driver. Will that be of any help? Any suggessions
are welcome.
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You need to debug your driver. You do not need the checked build of the
os to do this, nor do you need the checked build of your driver, as the
debugger can be used with both free and checked drivers and operating
systems.
Your checked driver however ought to have LOTS of debug print tracing
and a huge number of ASSERTs, all active in the checked build and
perhaps inactive in the free build. A live debugger should be attached
to your test system at all times. Dbgview doesn’t count.
Your test system must be configured to produce a system dump file, and
you should do post mortem analysis on the crash dump.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@yahoo.com
Sent: Thursday, December 20, 2001 12:00 AM
To: NT Developers Interest List
Subject: [ntdev] Machine Reboots …
Hi all,
i have a filesytem filter driver that boots the machine or
sometimes gives
a blue screen. This happens after a few hours on activating
the driver. How
should I debug the driver?
I am thinking of installing a checked build version of NT and
building the
checked version of the driver. Will that be of any help? Any
suggessions
are welcome.
Regards.
You are currently subscribed to ntdev as:
xxxxx@hollistech.com To unsubscribe send a blank email to
leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Analyze the crash dump first.
Add more and more ASSERTs and coverage prints to your code to know what place of your code behaves badly.
Coverage testing (testing which ensures that ALL code paths are executed at least once) is a good idea for such a situation.
Max
----- Original Message -----
From:
To: “NT Developers Interest List”
Sent: Thursday, December 20, 2001 12:00 AM
Subject: [ntdev] Machine Reboots …
> Hi all,
>
> i have a filesytem filter driver that boots the machine or sometimes gives
> a blue screen. This happens after a few hours on activating the driver. How
> should I debug the driver?
>
> I am thinking of installing a checked build version of NT and building the
> checked version of the driver. Will that be of any help? Any suggessions
> are welcome.
>
> Regards.
>
> —
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Because you’re developing a file system filter driver, which typically
relies on and works in conjunction with a large number of OS components
(Cc, Mm, etc), I think you should be testing your driver on a complete
checked build of the OS.
If you’re experiencing sudden reboot issues, you may be experiencing
multiple faults. In your case, as a file system driver, hitting a page
fault while the cache manager is calling you for paging IO to handle
someone else’s page fault (to page in memory). A complete checked build
should help you track that down.
Bryan S. Burgin
xxxxx@microsoft.com
-----Original Message-----
From: xxxxx@yahoo.com [mailto:xxxxx@yahoo.com]
Sent: Wednesday, December 19, 2001 4:00 PM
To: NT Developers Interest List
Subject: [ntdev] Machine Reboots …
Hi all,
i have a filesytem filter driver that boots the machine or sometimes
gives
a blue screen. This happens after a few hours on activating the driver.
How
should I debug the driver?
I am thinking of installing a checked build version of NT and building
the
checked version of the driver. Will that be of any help? Any suggessions
are welcome.
Regards.
You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com