I suggest you ...

Support debugging of C++ code with IntelliTrace

This suggestion is migrated to Developer Community. Please use below link to view the current status.
As a C++ developer I am always sad when seeing cool features only available for C#, VB, ... e.g. IntelliTrace would be really useful to get rid of these invisible, hidden, and not reproducable errors.

(see http://msdn.microsoft.com/de-de/library/dd264915.aspx)

765 votes
Sign in
Password icon
Signed in as (Sign out)
You have left! (?) (thinking…)
Julius Wachsmuth shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Password icon
Signed in as (Sign out)
  • Ken Lippert commented  ·   ·  Flag as inappropriate

    We have apps that blend newer C# code with older, established C++ routines. We would like to see Intellitrace useful throughout this environment.

  • Giles Middleton commented  ·   ·  Flag as inappropriate

    I wanted historical C++ (non .net!) debugging just now! Instead of restarting the exe to get back to the previous state.

  • Eric commented  ·   ·  Flag as inappropriate

    The VMware idea seems to support 2005 and 2008. Not sure I want to use such an old version, but it could be one way to at least get some functionality of historical debugging.

    On the other hand, running something in a VMWare VM or any VM definitely changes the timing, so I cannot get behind the idea that the replay debugging can take the place of the standalone collector, and I certainly cannot get behind the idea of using the VMWare replay debugging in any instance requires any graphics intensive application.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Why hasn't this gotten more support? Someone with a blog needs to post the link to this idea so developers will know about it and can vote if they want.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Yes, Yes, Yes!

    C++ is a viable platform, and probably more in need of good debugging tools than some of the other languages.

    As an ole time programmer, I am used to a certain level of debugging support from any compiler manufacturer. Frankly, Microsoft is not rising to the level of its predecessors.

    A trace log of program execution has been a basic version 1 feature in compilers since 1966. And now, with Visual Studio 2013, supposedly the best compiler on the market, this basic feature is not included? Why?

    This does not speak well of Microsoft.

  • ac commented  ·   ·  Flag as inappropriate

    code for implementing efficient deltas, faster and more efficient than xdelta. IDK how it compared to MS's own stuff.

Feedback and Knowledge Base