Thread Validator Tutorials
The Tutorials
Getting Started
User Interface Mode
How to interpret the thread validator displays
Analysing an Application
Good Lock Strategy
Deadlock using two threads
Potential deadlock caused by incorrect locking strategy.
Potential deadlock caused by an infinite wait.
Leaving an unlocked critical section.
Deleting a locked critical section.
Leaving a critical section in the wrong order.
Identifying deadlock objects when not collecting callstacks.
Analysing an existing deadlocked application.
Getting information about a threading error.
Detecting deadlocks in a child process
Detecting deadlocks in a service
Detecting deadlocks in a service child process
Detecting deadlocks in an IIS ISAPI DLL
Command Line Deadlock Detection in a Child Process
Analysing an Application
This tutorial uses the nativeExample application to demonstrate analysing an application showing various threading errors. Threading errors are usually complex, however, it is possible to demonstrate such errors using a sample program with specific errors built into the program. We have strived to keep the examples simple, even if in places they do seem contrived.
Please work through each Thread Validator tutorial as presented. Do not be tempted to perform one tutorial without closing the example program between tutorials – the tutorial may not behave as intended.
Before you begin
These tutorials are intended to be performed with the default settings shipped with Thread Validator.
If you have modified the settings, please reset them using the Reset button on the settings dialog.