![]() ![]() ![]() CTS is based on a trace from a hardware unit or from an instruction-set simulator, and the essence of what CTS adds is the ability to go back in time and investigate past state. Lauterbach is a big player in the embedded debug market, with their TRACE32 debugger. In 1999, Lauterbach launched the Context Tracking System, CTS. No reverse breakpoints, no support for proper processes, single-core only, capable of doing system-level bare-metal debug (since that was what most software was like back then).ġ999. Worked for PC software under DOS or early Windows versions. Based on single-stepping forward through assembly code and building an instruction history. In 1992, version 3 of the Borland Turbo Debugger had a feature called “reverse execution” that let you back up in the execution history, up to some 400 assembly instructions. Post updated to add Borland Turbo Debugger.ġ992. Post updated with a revised timeline for Lauterbach CTS. The first commercial product featuring reverse debugging was launched in 2003, and then there have been a steady trickle of new products up until today. ![]() Part one of this series provided a background on the technology and part two discussed various research papers on the topic going back to the early 1970s. In this final part of my series on the history of reverse debugging I will look at the products that launched around the mid-2000s and that finally made reverse debugging available in a commercially packaged product and not just research prototypes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |