I was wondering - how do Windows driver developers test themselves?
Lets say that I am debugging an unpleasant problem in the driver that I wrote. I want to be able to constantly add traces and logs, change small parts of the code, etc.
Each time I create a version of my driver and get a .sys file that I want to deploy to a test machine, and look at a tool like dbgview to understand what is going on. AFAIK, for code changes to be executed, the only way is to restart the test server.
It's horrible! This means that I have to wait a long time between making minor adjustments to the code and being.
Is this really so? Is there no way to tell windows to dynamically reload my driver?
If not, how do Windows driver developers work? Do they constantly reboot their test servers to make sure everything works for them?
source
share