-
Notifications
You must be signed in to change notification settings - Fork 217
Logging
Gregg Miskelly edited this page Jun 23, 2015
·
9 revisions
The MIEngine has logging in it to make it easy to see what commands we are sending to GDB/LLDB, what output GDB/LLDB is returning, and how long each command took.
If you have the MIEngine solution open and you are hitting F5 using the debug configuration, the logging is automatically on. Just open the output window (Debug->Windows->Output) and you can see the interactions that MIEngine is having with the target debugger.
Logging can also be enabled in a Visual Studio instance without needing to somehow patch the version of the MIEngine used by Visual Studio. To do so:
- Clone the sources:
git clone https://github.com/Microsoft/MIEngine.git - Enable logging:
src\MICore\SetMIDebugLogging.cmd on - Restart Visual Studio
- Try the scenario
- To turn logging back off, run
src\MICore\SetMIDebugLogging.cmd off - Open %TMP%\Microsoft.MIDebug.log
- SetMIDebugLogging.cmd has no dependencies, so you can copy it to another computer if you don't want to enlist on the target box.
- The name of registry keys changed after VS 2015 RC, so if you are using the RC build, these instructions will not work.
- If you are looking at Android scenarios, there is a '/serverlogging' argument to SetMIDebugLogging.cmd which can be used to turn on gdbserver logging