|
Things that can cause OutputDebugString messages not to get to the Monitor Viewer GUI tool:
| • | Are you running it under administration priveledges? If you are not an administrator the tool may not receive messages; right click the shortcut to the tool and configure it to run with administration priveledges. |
| • | Is the MS visual studio ide or another debugger running? Debuggers (including the MS visual studio ide) can capture DebugOutputStrings and prevent the tool from receiving them. |
| • | Is the viewer set to capture messages - there is a drop down combo box on the toolbar, make sure it is set to capture. |
| • | If you're still not having any luck, add the following to your main code to verify that debug logging is actually compiled in and working: |
JrDebug::WriteToFilename("demologoutput.log",false);
JrDebug::Announce("Test Application",true);
That will cause debug messages to be written to the file demologoutout.log, AND force the debug logger to generate an announcement log message even if debugging is disabled. If you dont see this it means debuglogging was not compiled into your code.
| • | If you are still get no output and suspect that JrDebugLogger is not being compiled in, you can insure it is by calling the following function which will trigger a compilation error if JrDebugLogging in not compiled into your code: |
JrDebug::ErrorIfNotCompiledIn();
|