Summary

[Previous] [Next]

Multithreaded programming is difficult and the area in which you'll encounter some of the hardest bugs you'll ever have to solve. This chapter presented tips and techniques that should help you avoid deadlocks from the beginning of your project. As I stressed early in the chapter, in multithreaded programming, up-front planning is vital, and you must make sure to allot your team enough time and resources to plan multithreaded applications carefully and correctly. Once you're faced with the inevitable multithreaded deadlocks, however, there's no need to panic: this chapter also covered DeadlockDetection, a utility that will allow you to figure out which threads deadlocked on which synchronization object.

Finally—and, I can't stress this point enough—if you're doing multithreaded programming, you must be developing, running, and testing your projects on multiprocessor computers. If you're not, you probably shouldn't be doing multithreaded programming because you're leaving yourself open to some extremely serious bugs.