Editing Turbo Pascal (section)

===Debugging and profiling===
The IDE provided several debugging facilities, including [[Program animation|single stepping]], examination and changing of variables, and conditional breakpoints. In later versions assembly-language blocks could be stepped through. The user could add [[breakpoint]]s on variables and registers in an IDE window. Programs using [[IBM PC compatible|IBM PC]] graphics mode could flip between graphics and text mode automatically or manually, or display both on two screens. For cases where the relatively simple debugging facilities of the IDE were insufficient, Turbopower Software produced a more powerful debugger, T-Debug.<ref>{{cite web |url=https://books.google.com/books?id=9j4EAAAAMBAJ&pg=PA26 |title=InfoWorld 21 Mar 1988: Announcement of Turbopower T-Debug 4 |date=21 March 1988 |access-date=2015-12-13 |archive-url=https://web.archive.org/web/20160425194704/https://books.google.com/books?id=9j4EAAAAMBAJ&pg=PA26&lpg=PA26 |archive-date=2016-04-25 |url-status=live}}</ref> The same company produced Turbo Analyst and Overlay Manager for Turbo Pascal. T-Debug was later updated for Turbo Pascal 4, but discontinued with the release of Borland's [[Turbo Debugger]] (TD), which also allowed some hardware intervention on computers equipped with the new [[80386]] processor.

TD was usually supplied in conjunction with the Turbo Assembler and the Turbo Profiler, a code [[profiler (computer science)|profiler]] that reported on the time spent in each part of the program to assist [[program optimisation]] by finding bottlenecks.<ref>{{cite web |url=http://www.textfiles.com/bitsavers/pdf/borland/Turbo_Profiler_1.0_Users_Guide_1990.pdf |title=Turbo Profiler 1.0 manual |access-date=2011-11-03 |archive-url=https://web.archive.org/web/20120402031845/http://www.textfiles.com/bitsavers/pdf/borland/Turbo_Profiler_1.0_Users_Guide_1990.pdf |archive-date=2 April 2012 |url-status=dead}}</ref> The books included with Borland Pascal had detailed descriptions of the [[Intel]] assembler language, including the number of clock cycles required by each instruction. Development and debugging could be carried out entirely within the IDE unless the advanced debugging facilities of Turbopower T-Debug, and later TD, were required.

Later versions also supported [[remote debugging]] via an [[RS-232]] communication cable.<ref>{{cite web |url=http://www.marcocantu.com/delphipowerbook/DebuggingDelphiPrograms.pdf |title=Marco Cantų's Delphi Power Book: Debugging Delphi Programs |access-date=2011-10-31 |archive-url=https://web.archive.org/web/20120331032317/http://www.marcocantu.com/delphipowerbook/DebuggingDelphiPrograms.pdf |archive-date=31 March 2012 |url-status=dead}}</ref>