Will IntelliTrace(tm) (historical debugging) be available for unmanaged c++ in future versions of Visual Studio?

I love the idea of historical debugging in VS 2010.

However, I am really disappointed that unmanaged C++ is left out.

IntelliTrace supports debugging Visual Basic and C# applications that use .NET version 2.0, 3.0, 3.5, or 4. You can debug most applications, including applications that were crea开发者_JAVA百科ted by using ASP.NET, Windows Forms, WPF, Windows Workflow, and WCF. IntelliTrace does not support debugging C++, script, or other languages. Debugging of F# applications is supported on an experimental basis.

(editorial) [This is really poor support in my opinion. .NET is less in need of this assistance than unmanaged c++. I an getting a little tired of the status of plain old C++ and its second-class status in the MS tools world. Yes, I realize it is probably WAAY easier to implement this with .NET and MS are pushing .NET as the future, and yes, I know that C++ is an "old" language, but that does not diminish the fact that there are lots of C++ apps out there and there will continue to be more apps built with C++. I sincerely hope MS has not dropped C++ as a supported developer tool/language- that would be a shame.]

Does anyone know if there are plans for it to support C++?

---

According to this MSDN blog post they "hope to fix this limitation in the future."

---

If at all possible, you can compile your C++ code in GDB which has reverse-debugging capabilities.

---

"Unmanaged C++" is a loose term. It can include raw assembly. Basically, each instruction can change memory in an essentially unpredictable way. IntelliTrace only works decently because it can grok IL. This is no coincidence, IL was designed to be much more suitable for automatic analysis than x86 assembly.