>Also, let me know if this ever comes to managed code.
For managed code, VS2010 (Ultimate) introduced Intellitrace for C# .NET code. It let you step "backwards" which is a form of "time travel".
Since 2010, people have wondered if Microsoft was going to introduce a similar debugging capability for C++. It looks like they did -- but instead of reusing the previous "Intellitrace" brand and calling it "Intellitrace for C++", they've labeled it "Time Travel Debugging".
Intellitrace and TTD take different approaches and have very different trade offs. Intellitrace allows imposing logging on a system posthoc. TTD records everything the system does.
They are not merely labeled differently they are different in kind. The consequences of those trade offs make the pragmatic use cases very different.
Intellitrace was always intended to head toward logging in production systems, which i believe it has achieved now. It’s unlikely you would TTD a server in production without a very good reason. It is possible for a Intellitrace log to not have enough information to debug a problem. A TTD trace has fundamentally captured everything, its bigger, a bit more unwieldy... but in a deeper sense it is complete.
For managed code, VS2010 (Ultimate) introduced Intellitrace for C# .NET code. It let you step "backwards" which is a form of "time travel".
Since 2010, people have wondered if Microsoft was going to introduce a similar debugging capability for C++. It looks like they did -- but instead of reusing the previous "Intellitrace" brand and calling it "Intellitrace for C++", they've labeled it "Time Travel Debugging".