👋🏾👋👋🏼 Welcome to the Undo Community

Hi All,Tis the season for a new release and our oncoming release 6.6 Manchego adds a number of new features and improvements. What’s New Log Jump for VS CodeLog Jump provides a powerful method for developers to jump from a log line of interest to the exact point in time where it was emitted. Log jump enables developers to leverage both log files and a recording in order to indicate where the failure is occurring (logs) and then pin point the exact root cause and time travel debug quickly in order to resolve the problem. Log jump is a killer feature that when leveraged, significantly accelerates the debugging workflow and developer productivity. This video shows how…     Reverse step commands stop at breakpointsWhen used, the reverse step command (including reverse-step, reverse-next and the corresponding Reverse Step Into and Reverse Step Out buttons in Visual Studio Code) in UDB will now stop the program’s execution if the program hits a breakpoint or watchpoint. This improvement brings the behavior of reverse operations into line and is consistent with forward time travel commands. Forward and reverse-stepi step operations remain in the same thread The stepi and reverse-stepi commands now step one instruction forwards or backwards within the current thread. You can also use reverse-stepi -any-thread to step back exactly one instruction back in history, potentially switching threads in the process. Again this improvement provides consistent behaviour between stepi / reverse-stepi and other time-travel commands. Improvements to the bookmarks feature in UDB CLIBookmarks are really useful but not if you create too many and litter them around your code. Now you have the ability to delete them as freely as you create them. Parallel Search Parallel Search is a performance-enhancement option that makes use of multi-core systems to speed up the performance of reverse navigation commands. We’ll be writing more about this and its benefits separately soon as its such a significant development. 🚨Note: this is disabled by default for customers and has to be enabled for use. Expanded technical support documentation for VS Code usersWe’ve expanded the technical documentation available for Time Travel Debugging in VS Code. The full details will be announced next week.In the meantime, feel free to contact your Customer Success Manager if you have any further questions about how you can benefit from these new product features.Zoe Product MarketingTeam Undo Related informationMore About Log Jump

Our complete VS Code extension is now available in the Visual Studio Code Marketplace. It’s called Time Travel Debug for C/C++.The new extension, called Time Travel Debug for C/C++, places superior time travel debugging capabilities at the fingertips of developers using VS Code. By enabling developers to time-travel forward and backward through code execution flow it: provides full visibility into the state of code at any point in its execution makes it much easier to get your head around and understand complex code accelerates root cause analysis and identification speeds up bug fixing. By debugging this way, programmers can conduct effective root cause analysis without needing to predict ahead of time what to log, and avoiding disruptive redeployments.To work, it requires an existing copy of UDB 6.5 or later, or a trial version of UDB.Time Travel Debug for VS Code​​​​​But let's skip to the end, what’s actually new? What’s new? Here’s a summary of the key capabilities added to VS Code:  Time travel debugging (aka reverse debugging) Navigate backward and forward through code executionReverse Step In/Out/Over join the familiar Step In/Out/Over Launch, Attach, or Replay a LiveRecorder recording. Continue and Reverse Continue, stopping at Breakpoints/Conditional Breakpoints/Watchpoints. Inspect global and local variable values at any point in your program’s execution history. Timeline - visually navigate and zoom through the execution flow Bookmarks - set bookmarks at any point in your program’s execution history. These appear on the timeline and can be jumped to Undo your last navigation action Evaluate expressions and call functions in the Debug Console at any point in your program’s execution history.  Get the extensionGet the Time Travel Debug extension C/C++And if you haven’t got a copy of UDB already, you can help yourself to a full featured 60-day free trial. Join our VS Code User GroupWe really appreciate your feedback and new feature suggestions. So join our user group to either ask questions, make suggestions and tell us what you think.Join the VS Code group Known limitations Data WatchpointsThe Visual Studio Code C/C++ extension doesn’t currently support setting data watchpoints from the Watch window (issue #1410). Open the Debug Console panel below the source code editor and type:-exec watch <variable_name>to set a data watchpoint on an expression, or-exec watch -l <variable_name>to set a data watchpoint on the memory location currently used to store a variable.Then use the blue navigation buttons in the debugging control panel to run forwards or backwards until the variable’s value or memory location’s contents changes.Refer to the GDB documentation for details of the watch command. Look for the Time Travel Debug C/C++ extension in the Visual Studio Code Marketplace