After debugging the program can be recompiled without debugging information to reduce its size. The debugger can then be started (Turbo Debugger does not debug within the development IDE). To use Turbo Debugger with source display, programs, or relevant parts of programs, must be compiled with Turbo Pascal or Turbo C with a conditional directive set to add debugging information to the compiled executable, with related source statements and corresponding machine code. The original Turbo Debugger was sold as a stand-alone product introduced in 1989, along with Turbo Assembler and the second version of Turbo C. TurboPower released T-Debug Plus 4.0 for Turbo Pascal 4.0 in 1988, but by then Borland's Turbo Debugger had been announced. Initially, a separate company, TurboPower Software, produced a debugger, T-Debug, and also their Turbo Analyst and Overlay Manager for Turbo Pascal for versions 1 to 3. Turbo Debugger can be used for programs not generated by Borland compilers, but without showing source statements it is by no means the only debugger available for non-Borland executables, and not a significant general-purpose debugger.Īlthough Borland's Turbo Pascal has useful single-stepping and conditional breakpoint facilities, the need for a more powerful debugger became apparent when Turbo Pascal started to be used for serious development. It is a full-screen debugger displaying both Turbo Pascal or Turbo C source and corresponding assembly-language instructions, with powerful capabilities for setting breakpoints, watching the execution of instructions, monitoring machine registers, etc. Turbo Debugger (TD) is a machine-level debugger for DOS executables, intended mainly for debugging Borland Turbo Pascal, and later Turbo C programs, sold by Borland.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |