Debug (command)
The line-oriented debugger DEBUG.EXE is an external command in operating systems such as DOS, OS/2 and Windows (only in 16-bit/32-bit versions). DEBUG can act as an assembler, disassembler, or hex dump program allowing users to interactively examine memory contents (in assembly language, hexadecimal or ASCII), make changes, and selectively execute COM, EXE and other file types. It also has several subcommands which are used to access specific disk sectors, I/O ports and memory addresses.
| DEBUG.COM (MS-DOS <= 2.0), DEBUG.EXE (MS-DOS >= 3.x) | |
|---|---|
 | |
| Original author | Tim Paterson |
| Developers | Microsoft, IBM, Digital Research, Novell, Caldera |
| Written in | MS-DOS: x86 assembly language |
| Operating system | DOS, OS/2, Windows |
| Type | Debugger |
| License | MS-DOS v2.0, FreeDOS: MIT OS/2, Windows: Proprietary software |
| Website | Debug |
The line-oriented debugger DEBUG.EXE is an external command in operating systems such as DOS, OS/2 and Windows (only in 16-bit/32-bit versions[1]).
DEBUG can act as an assembler, disassembler, or hex dump program allowing users to interactively examine memory contents (in assembly language, hexadecimal or ASCII), make changes, and selectively execute COM, EXE and other file types. It also has several subcommands which are used to access specific disk sectors, I/O ports and memory addresses.
Overview
[edit]
DEBUG.COM (among other commands) in IBM PC DOS 1.0.
DEBUG.EXE commandTraditionally, all computers and operating systems have included a maintenance function, used to determine whether a program is working correctly.[citation needed] DEBUG was originally written by Tim Paterson to serve this purpose in 86-DOS. When Paterson began working for Microsoft in the early 1980s he brought the program with him. DEBUG was part of DOS 1.00 and has been included in MS-DOS/PC DOS and certain versions of Microsoft Windows. Originally named DEBUG.COM, the executable was renamed into DEBUG.EXE with MS-DOS 3.2.[2]
Windows XP and later versions included DEBUG for the MS-DOS subsystem to maintain MS-DOS compatibility. The 16-bit DOS commands are not available on 64-bit editions of Windows.[3]
The MS-DOS/PC DOS DEBUG has several limitations:
- In assembly/disassembly modes it only supports 8086 opcodes.
- It can only access 16-bit registers and not 32-bit extended registers.
- When the "N" subcommand for naming files is used, the filename is stored from offset DS:5D to DS:67 (the Program Segment Prefix File Control Block area), meaning that the program can only save files in FAT 8.3 filename format.
Enhanced DEBUG packages include the DEBUG command in Novell DOS 7, OpenDOS 7.01 and DR-DOS 7.02 and higher, a reimplementation of Digital Research's former Symbolic Instruction Debugger SID/SID86,[4] which came with former versions of DR DOS.[5][6][7] It is fully compatible with the DEBUG command line syntax of MS-DOS/PC DOS, but offers many enhancements, including supporting 16-bit and 32-bit opcodes up to the Pentium, an extended mode (/X) with dozens of additional commands and sub-modes, a much enhanced command line syntax with user-definable macros and symbolic debugging facilities with named registers, loaded symbol tables, mathematical operations and base conversions, as well as a commenting disassembler.[8][7] Some versions also utilized DPMS to function as a "stealth mode" protected-mode debugger.[9]
The FreeDOS version of DEBUG was developed by Paul Vojta and is licensed under the MIT License.[10]
A 32-bit clone "DEBUGX" version supporting 32-bit DPMI programs exists as well.[11] Andreas "Japheth" Grech, the author of the HX DOS extender, developed enhanced DEBUG versions 0.98 to 1.25, and former PC DOS developer Vernon C. Brooks added versions 1.26 to 1.32.[12]
Syntax
[edit]DEBUG [[drive:][path] filename [parameters]]
When DEBUG is started without any parameters the DEBUG prompt, a "-" appears. The user can then enter one of several one or two-letter subcommands, including "A" to enter the assembler mode, "D" to perform a hexadecimal dump, "T" to trace and "U" to unassemble (disassemble) a program in memory.[13] DEBUG can also be used as a "DEBUG script" interpreter using the following syntax.
DEBUG < filename
A script file may contain DEBUG subcommands and assembly language instructions.[14] This method can be used to create or edit binary files from batch files.[2]
Debugging Subcommands
[edit]The following is a list of the DEBUG commands available from DEBUG.EXE in MS-DOS 6.22 via the ? command.
assemble A [address] compare C range address dump D [range] enter E address [list] fill F range list go G [=address] [addresses] hex H value1 value2 input I port load L [address] [drive] [firstsector] [number] move M range address name N [pathname] [arglist] output O port byte proceed P [=address] [number] quit Q register R [register] search S range list trace T [=address] [value] unassemble U [range] write W [address] [drive] [firstsector] [number] allocate expanded memory XA [#pages] deallocate expanded memory XD [handle] map expanded memory pages XM [Lpage] [Ppage] [handle] display expanded memory status XS
The R command displays the current register status and values
AX=0000 BX=0000 CX=0000 DX=0000 SP=FFEE BP=0000 SI=0000 DI=0000 DS=2A63 ES=2A63 SS=2A63 CS=2A63 IP=0100 NV UP EI PL NZ NA PO NC 2A63:0100 0F DB 0F
While D dumps the current memory displaying both hexadecimal and ASCII values
2A63:0100 0F 00 B9 8A FF F3 AE 47-61 03 1F 8B C3 48 12 B1 .......Ga....H.. 2A63:0110 04 8B C6 F7 0A 0A D0 D3-48 DA 2B D0 34 00 52 2A ........H.+.4.R\* 2A63:0120 00 DB D2 D3 E0 03 F0 8E-DA 8B C7 16 C2 B6 01 16 ................ 2A63:0130 C0 16 F8 8E C2 AC 8A D0-00 00 4E AD 8B C8 46 8A ..........N...F. 2A63:0140 C2 24 FE 3C B0 75 05 AC-F3 AA A0 0A EB 06 3C B2 .$.<.u........<. 2A63:0150 75 6D 6D 13 A8 01 50 14-74 B1 BE 32 01 8D 8B 1E umm...P.t..2.... 2A63:0160 8E FC 12 A8 33 D2 29 E3-13 8B C2 03 C3 69 02 00 ....3.)......i.. 2A63:0170 0B F8 83 FF FF 74 11 26-01 1D E2 F3 81 00 94 FA .....t.&........
And Unassemble displays the attempted disassembly of the same memory
2A63:0100 0F DB 0F 2A63:0101 00B98AFF ADD [BX+DI+FF8A],BH 2A63:0105 F3 REPZ 2A63:0106 AE SCASB 2A63:0107 47 INC DI 2A63:0108 61 DB 61 2A63:0109 031F ADD BX,[BX] 2A63:010B 8BC3 MOV AX,BX 2A63:010D 48 DEC AX 2A63:010E 12B1048B ADC DH,[BX+DI+8B04] 2A63:0112 C6F70A MOV BH,0A 2A63:0115 0AD0 OR DL,AL 2A63:0117 D348DA ROR WORD PTR [BX+SI-26],CL 2A63:011A 2BD0 SUB DX,AX 2A63:011C 3400 XOR AL,00 2A63:011E 52 PUSH DX 2A63:011F 2A00 SUB AL,[BX+SI]
Using for non-debugging purposes
[edit]The DEBUG utility is useful for editing binary files in an environment where only DOS is installed without anything else. It can also be used to edit disk sectors, which is one method of removing boot-sector viruses.
Availability
[edit]Although technical documentation for the DEBUG command was removed with the release of MS-DOS 3.3, the command was retained in the standard distribution, unlike what was done with EXE2BIN.[15]
Other operating systems
[edit]The operating systems Intel ISIS-II[16] and iRMX 86,[17] DEC TOPS-10[18] and TOPS-20,[19] THEOS/OASIS,[20] Zilog Z80-RIO,[21] Stratus OpenVOS,[22] PC-MOS,[23] and AROS[24] also provide a DEBUG command.
See also
[edit]- List of DOS commands
- DDT (CP/M command) (Dynamic Debugging Technique)
- SID (Symbolic Instruction Debugger)
- SYMDEB
- CodeView
- Turbo Debugger
- SoftICE
- DEBUG (tag)
References
[edit]- ^ According to Microsoft Macro Assembler Reference, inline assembly is not supported for x64.
- ^ a b Sedory, Daniel B. "A Guide to DEBUG". Retrieved 2014-11-29.
- ^ MS-DOS subsystem commands
- ^ SID-86 User's Guide for CP/M-86 (2 ed.). Digital Research. August 1982 [March 1982]. SID86UG.WS4. Archived from the original on 2019-10-20. Retrieved 2020-02-06. [1] (NB. A retyped version of the manual by Emmanuel Roche with Q, SR, and Z commands added. This manual is for the CP/M-86 version, but the DR DOS version is similar.)
- ^ Born, Günter [in German] (1993). DOS 6 Tuning (in German) (1 ed.). Markt & Technik. ISBN 3-87791-495-0. (NB. Has several pages on MS-DOS DEBUG.EXE as well as on the Symbolic Instruction Debugger SID.EXE in DR DOS 5.0/6.0.)
- ^ Paul, Matthias R. (1997-05-24) [1991]. DRDOSTIP.TXT — Tips und Tricks für DR DOS 3.41 - 5.0 (in German) (47 ed.). Archived from the original on 2016-11-07. Retrieved 2016-11-07.
{{cite book}}:|work=ignored (help) (NB. Has some information on Symbolic Instruction Debugger (SID86.EXE in DR DOS 3.41 and SID.EXE in DR DOS 5.0/6.0), the predecessor of the DR-DOS DEBUG.EXE.) - ^ a b Paul, Matthias R. (2002-01-09). "SID86". Newsgroup: comp.os.cpm. Retrieved 2018-04-08.
[…] Since the DR-DOS 7.03 DEBUG is still based on the old SID86.EXE, I suggest to run DEBUG 1.51 and enter the extended help system with ?? from the debug prompt. This will give you eight screens full of syntax and feature help. Some of these features were also supported by older issues. […]
- ^ Paul, Matthias R. (1997-07-30). "Kapitel II.5. Allgemeines: Undokumentierte Möglichkeiten von DEBUG" [Undocumented features of DEBUG]. NWDOS-TIPs — Tips & Tricks rund um Novell DOS 7, mit Blick auf undokumentierte Details, Bugs und Workarounds. Release 157 (in German) (3 ed.). Archived from the original on 2017-09-10. Retrieved 2014-09-06.
{{cite book}}:|work=ignored (help) (NB. NWDOSTIP.TXT is a comprehensive work on Novell DOS 7 and OpenDOS 7.01, including the description of many undocumented features and internals. It is part of the author's yet larger MPDOSTIP.ZIP collection maintained up to 2001 and distributed on many sites at the time. The provided link points to a HTML-converted older version of the NWDOSTIP.TXT file.) - ^ Paul, Matthias R. (2001-04-09). NWDOS-TIPs — Tips & Tricks rund um Novell DOS 7, mit Blick auf undokumentierte Details, Bugs und Workarounds. Release 183 (in German) (3 ed.).
{{cite book}}:|work=ignored (help) - ^ "FreeDOS 1.2 Updates Package - debug (FreeDOS Base)". Ibiblio.org. 2021-02-16. Retrieved 2022-09-08.
- ^ Vojta, Paul. "DEBUG README". Archived from the original on 2007-08-24. Retrieved 2007-06-25.
- ^ Brooks, Vernon C. (2014-04-08). "Enhanced DEBUG for PC DOS and MS-DOS". PC DOS Retro. Archived from the original on 2020-02-21. Retrieved 2014-05-08.
- ^ "Microsoft TechNet Debug article". Retrieved 2008-04-23.
- ^ Irvine, Kip R. (2010). "Using Debug". Assembly language for Intel-based computers (PDF) (6th ed.). Prentice Hall. ISBN 978-0-13602212-1. Retrieved 2014-03-18.
- ^ Dror, Asael (1988-01-12). "Thank You, IBM". PC Magazine. p. 366.
- ^ ISIS II Users Guide
- ^ iRMX 86 Introduction And Operator's Reference Manual For Release 6
- ^ TOPS-10 Operating System Commands Manual (PDF). Digital Equipment Corporation. August 1980. Archived from the original (PDF) on 2020-08-09. Retrieved 2019-02-17.
- ^ "TOPS-20 Command manual" (PDF). Archived from the original (PDF) on 2020-08-09. Retrieved 2018-07-18.
- ^ THEOS/OASIS User′s Handbook
- ^ "Z80-RIO Operating System User's Manual" (PDF). Archived from the original (PDF) on 2022-01-28. Retrieved 2019-05-04.
- ^ "OpenVOS Commands Reference Manual" (PDF).
- ^ PC-MOS User Guide
- ^ "AROS Research Operating System". Archived from the original on 2019-07-02. Retrieved 2025-08-09.
External links
[edit]