For some reason I have started receiving dumps from production that require running .imgscan /l
first.
Now I tend to run small queries against the dump using CDB invoked from a powershell script. However, running .imgscan /l
every time takes considerable amount of time.
Is it possible to fix the dump in a way that renders .imgscan /l
unnecessary?
P.S.
I think there is another problem with the need to run .imgscan /l
- DebugDiag does not seem to understand such dumps.
After .imgscan /l
has found the headers and assigned them to modules, .dump /ma file.dmp
seems to write these information into a new dump file, making .imgscan
unnecessary when examining the new dump file.