I am developing a UMDF driver, and I am able to use its PDB
file to confirm events/function calls during its lifetime. However, I am also able to capture events prior to its DriverEntry
function. This events have become a concern for me, because I suspect that they alter some values initialized by the driver, thereby causing issues. I would like to know more about these events, but information on TraceView
shows them as 'Unknown' as shown below:
Is there a way to capture these trace logs better? It seems like the driver pdb does not contain information for these logs to show up correctly.
EDIT: I extracted TMF
files from my PDB
file using tracepdb
, and it seems like I do not have a TMF file that corresponds to the message GUIDs that are marked "No format information found"
. Could it be that these trace messages are from external entities, and not coming from the driver?
question from:
https://stackoverflow.com/questions/65878628/traceview-able-to-capture-logs-occurring-during-driver-installation-but-shown-a 与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…