dbgeng

问题 Is there a way from WinDbg, without using the DbgEng API, to display the symbol server paths (i.e. PdbSig70 and PdbAge) for all loaded modules? I know that lml does this for the modules whose symbols have loaded. I would like to know these paths for the symbols that did not load so as to diagnose the problem. Anyone know if this is possible without having to utilize the DbgEng API? edited: I also realize that you can use !sym noisy to get error messages about symbols loading. While this does

问题 Is there a way from WinDbg, without using the DbgEng API, to display the symbol server paths (i.e. PdbSig70 and PdbAge) for all loaded modules? I know that lml does this for the modules whose symbols have loaded. I would like to know these paths for the symbols that did not load so as to diagnose the problem. Anyone know if this is possible without having to utilize the DbgEng API? edited: I also realize that you can use !sym noisy to get error messages about symbols loading. While this does

问题 I am trying to write an extension function that will run to the next call and then print out information about the next instruction. I am using IDebugControl::Execute to run tc . As noted in the documentation, this call returns before the tracing has actually occurred. Sleeping or calling DispatchCallbacks does not see the tc trace occur before my extension returns. How can I allow the trace to happen without returning from the call? If I add my own DebugEventCallback then I can get notified