<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=1734298&amp;fmt=gif">

Newsletter #1 - 3 tips to become a Debugging Pro

Posted by Alice Gajos

One morning a few weeks back, on our Linkedin Page we've received a comment from Shaon:
"What happened to TimeMachine??!"
The answer is: "Time Machine for Visual Studio became an Ultra Tool - RevDeBug!"

And here are 3 tips on how to use it to become a debugging pro:

Understand all aspects of the technical architecture and how different components play together

Yep, but who has enough time for that? When the bug appears usually, we have limited time to find the root cause of the problem. But there is a tool, which allows you to inspect the behavior of your application in detail. Check out this article to get to know more.

Identify the right debugging technology for your stack

Traditional debugging takes time. Sometimes, a lot of time, especially if an unhandled exception is hidden deep within the code, or the bug has caused throughout a program, with multiple negative repercussions. The answer to those problems is reverse debugging technology. How does it work in practice?

Figure out the code paths

The information on which parts of your code were executed during the troublesome session of the application might be a key to understand what really happened. Although it is not the main function of RevDeBug, code coverage data is also a great help in bug inspecting and code refracturing. Would you like to know more about this tool? Check out how performance profiler works.

Download for free