News & Updates
Get the latest on our products and on Undo!
On-Demand Webinar ACCU conferences have a long tradition of high quality sessions covering many technical aspects of software development.This year, Undo delivered a technical lunch and learn session focussing on demonstrating the benefits of Time Travel Debugging - including a world exclusive sneak peak of our new VSCode IDE integration.Click to watch: https://digital-medium-co-uk.zoom.us/rec/play/EKYDCkojN5tYbdXtJZAP1IUdrTam2CPHcH7en-T5kueUFI3E-xcWMLpQrOgpNFUxbeblUh05i71R8T3d.WcUKoCHaM-8JxT0j?continueMode=true AbstractTime Travel Debugging simplifies debugging by letting developers freely step backwards, as well as forwards, through a program’s execution. In this practical lunch and learn session we’ll demonstrate benefits of Time Travel debugging and show how it delivers a radically simplified workflow for debugging, compared to traditional methods of debugging forwards. Our Engineer will walk through how developers can simplify fixing bugs by: Deterministically capturing and rep
On-demand WebinarSpeakers: Greg Law (Founder/ CEO - Undo) & Dewang Li (Solutions Architect - Synopsys)Click to watch (90 mins deep dive) AbstractAn overview of how some of the seemingly-magical modern Linux C++ tools actually work so that you can get the most from them. C++ is a language and ecosystem that is unashamedly close to the metal, and to be an expert practitioner an understanding of compiler and OS fundamentals is essential, and this includes debugging and profiling tools. The last decade has seen a ‘cambrian explosion’ in tooling: Valgrind, perf, Address Sanitizer, rr, Live Recorder, Coverity and cppcheck have either arrived or become mainstream and even good old GDB has come a long way. Greg gives an overview of how these amazing/magical tools are implemented often exploiting a combination of compiler, OS and CPU features. Contains details on ptrace, DWARF debug info, how static analyzers work, record and replay systems - so that you can select the right tool for the j
Last week, Facebook Engineering shared with the world how (and why) they are using reverse debugging at scale. Their use case and approach is very different to ours, but shows that the world of engineering is coming round to what we and our customers already know.Yeah they have a ring buffer of some fixed size. This is kind of how @undo_io works although it uses binary instrumentation rather than Intel PT as I understand it.— Kyle Huey (@khuey_) April 30, 2021 Apart from being a heavy-weight endorsement of reverse debugging (we’ve noted that Facebook seem reluctant to adopt ‘time travel debugging’, the name for same thing coined by Microsoft - LOLZ ), it’s interesting to get insight into how Facebook are using it in production. Read the post
Hi community people 👋🏾,The main purpose of this community is that we want our valued customers and wider community of Time Travel Debugging friends to be the first to know about what’s coming next.Every quarter, we deliver a substantial quarterly release update to our products (with smaller incremental releases in between of course) with the intention of continuously improving usability and performance. Our next quarterly release will be dropped in early June and so it is time to tease the exciting things that will be in it. Status Prompt - for our die hard command-line users, there will be a useful update to the command-line prompt to make it more informative, contextual and smart. It will provide you with an interactive prompt that will give you more information about the status of your debuggee and what’s happening at that moment. Introducing the new time travel controls enabling you to undo/redo (ugo undo/redo) what you last did as you explore your code execution. Parallel Se
Brian Kernighan famously said, “Everyone knows that debugging is twice as hard as writing a program in the first place. So if you’re as clever as you can be when you write it, how will you ever debug it?”. For me, this doesn’t just mean “keep it simple.” It also means debugging is central to programming – you cannot be a great programmer without being great at debugging. Hopefully, my favorite C++ debugging tips will help you be as clever and productive debugging your code as you are writing it in the first place.#1 Have a full kit of debugging tools #2 Conditional breakpoints #3 Watchpoints #4 User-defined debugging commands in Python #5 Pretty-print structures #6 Time Travel Debugging #7 Command find to search for a byte sequence Want more C++ debugging tips? Read full article on the JetBrains Blog (external link):
We’re excited to announce our UDB early access beta preview of Undo’s new C/C++ extension (called Time Travel Debug) for Visual Studio Code (VS Code). Time Travel Debug will enable developers to unlock the power of UDB’s Time Travel Debugging capabilities to speed up error resolution, in Microsoft's hugely popular Visual Studio Code editor.This beta release delivers the following:User interface (UI) additions in VS Code for reverse navigation commands and time-travel commands. Support for loading LiveRecorder recordings. Support in the UI for UDB’s Bookmark and Log Jump features. Support for local debugging on Linux and for remote debugging using the Remote - Containers, Remote - SSH or Remote - WSL Visual Studio Code extensions.Our early access beta program gives developers the chance to try out UDB Time Travel Debugger in VS Code and share your product experience with us to help us take the UDB time travel debugging experience to the next level.Important things to knowYou’ll be the f
Already have an account? Login
Login to the community
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.