The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
windbg occasionally locked a pdb file in memory after a sys file on the target got unloaded, making it impossible to do a new build without closing windbg, but on the latest WDKs windbg this haoppens almost every time (and yes, the drivers unload handler got hit, and it is no longer in the lm list)
It used to be possible to clear this with a .reload /u , but this doesnt seem to work, so windb needs to be restarted.
Is there any other way to do this? It is a PITA to have to restart windbg everytime
|Upcoming OSR Seminars|
|OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!||Kernel Debugging||30 Mar 2020||OSR Seminar Space|
|Developing Minifilters||15 Jun 2020||LIVE ONLINE|
|Writing WDF Drivers||22 June 2020||LIVE ONLINE|
|Internals & Software Drivers||28 Sept 2020||Dulles, VA|