This project has moved and is read-only. For the latest updates, please go here.


Debug tracing support


DirectXTK makes use of C++ exception handling, which makes debugging somewhat difficult for developers new to EH usage.

This work item is to add OutputDebugString tracing to common failure points just before throwing exceptions in the DEBUG builds of the library.
Closed Dec 17, 2013 at 10:26 PM by walbourn


walbourn wrote Nov 14, 2013 at 7:36 AM

Note that Visual Studio's "Break on C++ Exception" debug setting is the best way to inspect C++ exceptions in a debugging session, but it requires some skills with callstacks and code inspection to notice the root cause of the throw quickly. These messages would be targeted to the most common issues like missing data files rather than every possible failure.

walbourn wrote Dec 11, 2013 at 6:16 AM

This kind of tracing support is used in the DirectXTK for Audio component. It just needs to be added to the rest of the library.

walbourn wrote Dec 17, 2013 at 10:11 PM

Implementing a "DebugTrace" helper in PlatformHelpers.h to make it cleaner to add this kind of tracing to the library...

walbourn wrote Dec 17, 2013 at 10:26 PM

Resolved with changeset 32623: DirectXTK: DebugTrace internal function usage