The Events Display

The ‘Events’ window shows you the threads that the program has started, the DLLs that were loaded/unloaded on the program’s behalf, etc.

The debugger will show the output of the ‘OutputDebugString’ Win32 function in this window.

If your message uses the Win32 API function ‘OutputDebugString’, all debug strings will be displayed in this window. Note that this does not trigger a breakpoint.

Here, the exact sequence of actions when a trap occurs will be displayed, if there is a problem with the debugger.

A DLL is loaded. The debugger displays its name, the file handle for the executable, the base of the DLL code, the offset to the debug information (if any), the pointer to the DLL name, and whether or not it is a Unicode DLL.

The OutputDebugString event is received. The debugger is currently unable to understand the undocumented formats that are used by Microsoft’s DLLs. Further investigation of this may produce a more interesting display here. Normally a character string should be at the address pointed to by lpDebugStringData, but this is not the case for system DLLs.