Following up on
this post, Microsoft has confirmed this to be a bug in version 6.6.7.5 of
windbg. The good news is that the fix is scheduled to appear in the next release. The bad news is that, while there's no official date for that release, ballpark estimates from Microsoft indicate that it won't be for another 3 months or so.
Posted
Jan 22 2007, 10:44 AM
by
mike-woodring