This tutorial describes how to set up Bug Validator to include or exclude different source files from instrumentation processing when you are dynamically linking your application with MFC and/or the C Runtime. For each use case (exclude and include) we’re going to provide a short video followed by step-by-step instructions.
When you dynamically link to MFC and the CRT, the code for MFC and the CRT is held in separate DLLs to your application. This allows you to specify not to process MFC or CRT code by simply indicating which DLLs not to process – you don’t need to know where the source code for those DLLs is.
To exclude MFC, CRT, and STL source files from instrumentation do this:
Future execution traces will not include information relating to any source files in the excluded DLLs.
When you dynamically link to MFC and the CRT, the code for MFC and the CRT is held in separate DLLs to your application. This allows you to specify to process MFC or CRT code by simply indicating which DLLs to process – you don’t need to know where the source code for those DLLs is.
To include MFC, CRT, and STL source files from instrumentation do this:
Future execution traces will include information relating to any source files in the included DLLs.