Tiburon Preview: Vista Wait Chain Traversal

I see that several of my co-workers have started blogging about new features in Tiburon, the upcoming release of Delphi and C++Builder.  If you haven’t already, check out what Allen, Nick, Chris, and Seppy are saying.  For the Tiburon release cycle, since much of the debugger had previously been Unicode-enabled, I’ve been working on mostly non-debugger things, including being heavily involved in the "Unicodification" of the other parts of the IDE.  That said, those of us on the debugger team were still able to include a few new features in Tiburon.  This article will describe one of the new features.

In Tiburon, we’ve added support for Vista Wait Chain Traversal.  Wait Chain Traversal is made possible by new APIs included in Windows Vista and Windows Server 2008, and as such, this new debugger feature is only available if you are running on one of those OSes.  For reference, the MSDN link that describes this feature is http://msdn.microsoft.com/en-us/library/ms681622.aspx.

This feature allows you to get detailed information about thread deadlocks that occur in your program.  This can make it much easier to debug problems that traditionally have been very hard to debug.  Not all types of thread deadlocks can be debugged using Wait Chain Traversal.  As mentioned in the above referenced MSDN article:

WCT currently supports the following synchronization primitives:

• ALPC
• COM
• Critical sections
• Mutexes
• SendMessage
• Wait operations on processes and threads

To give a sense of how this feature is implemented in Tiburon, I’ve included the following screenshot:

You’ll see that in the Thread Status view, a new column, titled "Wait Chain" is shown.  This column only shows up if you’re running on an OS that supports Wait Chain Traversal.  In the screenshot, a program that is deadlocked has been paused in the debugger.  Let’s take a look at what the new column in the thread view is telling us:

1. The main thread is blocked waiting on Thread.  In this case the main thread has called WaitForSingleObject on a thread handle.  The thread being waited on is the thread with a "Threaad Id" of 3792 (the third thread in the list)
2. The thread being waited on is, itself, blocked.  In this case it is waiting for a SendMessage call to return. The message has been sent to a window that is owned by thread 2792 (the second thread in the list)
3. That thread (2792) in turn is waiting to get access to a CriticalSection.  Basically, the message loop for this window, in response to the message sent by thread 3792, has asked for a CriticalSection.  However, as you can see, that CriticalSection is currently owned by thread 3792.

So basically, we have two threads (1284 and 2792) that are waiting for a third thread (or for a resource owned by that thread).  That thread in turn is also blocked, waiting for something on one of the other threads.  This leads to the deadlock.  The intention is that with the extra information about each thread involved in the deadlock, it will be much easier to debug and fix the problem leading to the deadlock.  This is a welcome addition to the OS and in turn to Delphi and C++Builder.

One final note:  Although the above screen shot shows this feature using a C++Builder test case, Wait Chain Traversal also works with native Delphi programs.

Share This | Email this page to a friend

Posted by Chris Hesik on July 21st, 2008 under CodeGear Debugger |