tlum
February 4th, 2005, 01:36 PM
This is really a tools and/or debugging question… but related to a driver.
I am debugging a kernel fault caused by an invalid memory reference in a driver's DPC. It’s a 3rd party driver and the .pdb is not going to be available. I would like to be able to create my own symbolic references to certain functions, variables and structures as I go through the kernel dumps in WinDbg and also be able to persist them between sessions.
Is there any relatively easy way to manually create a simple symbol file that WinDbg will accept to go along with the driver image in the kernel dump? Is there another means to annotate functions and variables in a kernel dump and persist them across sessions? Is there a more appropriate place to ask this question?
Thanks,
-Ted-
I am debugging a kernel fault caused by an invalid memory reference in a driver's DPC. It’s a 3rd party driver and the .pdb is not going to be available. I would like to be able to create my own symbolic references to certain functions, variables and structures as I go through the kernel dumps in WinDbg and also be able to persist them between sessions.
Is there any relatively easy way to manually create a simple symbol file that WinDbg will accept to go along with the driver image in the kernel dump? Is there another means to annotate functions and variables in a kernel dump and persist them across sessions? Is there a more appropriate place to ask this question?
Thanks,
-Ted-