We find the root cause
of the problem

Analysis and Debugging of Application Failures in Production, Staging and Test Environments

A Three-day Workshop

Background

Visual Studio is not usually installed in Production Environments. It is reasonable to assume that Visual Studio is not installed at your customer’s site. Field technicians, engineers, QA and QC departments in development organizations and developers who are sent to solve problems at a customer’s site often experience difficulties in debugging and analyzing an application. Visual Studio is not usually installed in Production Environments. It is reasonable to assume that Visual Studio is not installed at your customer’s site. Field technicians, engineers, QA and QC departments in development organizations and developers who are sent to solve problems at a customer’s site often experience difficulties in debugging and analyzing an application.
However, even the most “sterile” environments contain built in OS tools that, with proper use, can enable you to receive sufficient information to track down the reason for a program crash. Tools that don’t require installation can help you find the exact source file and line number that caused the program failure. It can also supply the developer with a stack trace and local variables at the time of the call that caused the crash.
The workshop offers original material based on field experience and information taken from little-known Microsoft support articles and documentation. . The workshop is practical and the participants will practice the techniques in a lab environment. There isn’t any official MOC course with the information given in this workshop. The participants will get valuable practical knowledge necessary for anyone who has to trace bugs in the field. During the workshop, developers will be exposed to tools, techniques and skills that are not part of the normal day-to-day development environment. Support personnel will get tools which will help them collect data required by developers; data that will enable developers to find the root cause of failure quickly.

Target Audience

Support personnel of production and staging environments; Helpdesk personnel; Testers in test and QA environments; Developers tracing bugs in dumps; Developers in the field or at a customer’s site.
The uniqueness of this workshop is that it is suitable for developers, support personnel and field engineers alike.

Pre-requisites

Knowledge of programming and practical experience in debugging problems.

Main Topics:

  • Debugging tools for Windows package.
  • Extracting a dump from a program.
  • Dump types and how to choose the right type.
  • Debugging OS failures.
  • Event tracing tools and usage.
  • Debug Diag tool.
  • WMI fundamentals.
  • Non Invasive debugging.
  • Just in time debugging.
  • WinDbg, CDB, KD and NTSD.
  • Tools that do not require installation.
  • Basic scripting for debugging.
  • Incorporating source into the debugging process.
  • Tips, tricks and lessons learnt in the field.
  • OS Symbols packages.
  • Analyzing dumps.
  • Performance counters tools and usage.
  • Tools and techniques to automate diagnostic data gathering.
  • Gflags fundamentals.
  • System logs analysis and proper usage.
  • Live debugging constraints and proper usage.
  • symbols server.
  • The "Foot print" of the tools and its effect on production.
  • Configuring the OS for maximum usable analysis data gathering.
  • Making the application more crash friendly.
  • BSOD fundamentals.