"The problem with traditional debugging is that you can see the failure but not why it happens. With Undo we’re able to debug the impossible problems and see what caused them. It is now one of our most important tools for these customer-critical situations using it for these problems has delivered real value and we can also see the productivity gains it provides for day-to-day debugging."
"As soon as the code failed we got experts on the line and they were able to use the recording generated by Out-and-About* to step backwards and forwards line by line using UndoDB. We found the bug in three hours, and it then took just two hours to solve, which was a huge win after three months of searching using other methods. Given its nature we simply couldn’t have found it through source code analysers, as it was generated within dynamic code."








