As-is the module lookups can fail for existent modules, or can return the
wrong module.
The module paths yielded from the NT Kernel Log sometimes start with a
backslash, without any indication of the drive letter that stores the module
file.
The module resolution machinery should search all local drives for the
module, and should verify the checksum and size for any module found.
Original issue reported on code.google.com by si...@google.com on 14 Feb 2010 at 11:47
Original issue reported on code.google.com by
si...@google.com
on 14 Feb 2010 at 11:47