home *** CD-ROM | disk | FTP | other *** search
- Copyright (C) 1992 MetaWare Incorporated. All Rights Reserved.
-
- 32-Bit Source-Level Debugger
- Version 1.3 for Extended DOS 80386/486
- April 1992
-
- ------------------------------------------------------------------------------
- NOTE: See README.WIN for information about MDBW, the Windows version of the
- MetaWare Debugger.
- ------------------------------------------------------------------------------
-
-
- Table of Contents
- -----------------
- 1. Configuring the Debugger
- 2. Demonstration Script MDBDEMO.BAT
- 3. Additions/Corrections to Printed Documentation
- 4. Miscellaneous
- 5. AutoCAD Development System
- 6. Known Problems
-
-
- 1. Configuring the Debugger
- ----------------------------
-
- You must set environment variable MDBENV to the location of file MDB.ENV, and
- environment variable MDBHELP to the directory in which the help files reside.
- For example:
-
- set MDBENV=c:\hc386\bin\mdb.env
- set MDBHELP=c:\hc386\bin
-
- By default, the debugger looks for its configuration file (MDB.CNF) and its
- help files (MDB.TXT, MDB.BOD, and MDB.IDX) in the directory in which the
- debugger executable (MDB1.EXP) is found.
-
-
- 2. Demonstration Script MDBDEMO.BAT
- -----------------------------------
-
- Once you have installed the compiler and set a path to the compiler BIN
- subdirectory, you can run the debugger demo by typing:
-
- MDBDEMO
-
- File MDBDEMO.BAT is in the compiler BIN subdirectory. This batch file runs
- program MDBDEMO.CPP (which is in the DEMOS\CPP directory) with a journal file.
- The demo can take anywhere from 10 to 20 minutes depending on the speed of the
- machine.
-
-
- 3. Additions/Corrections to Printed Documentation
- --------------------------------------------------
-
- * Macros you define for function keys F1-F10 work only when the Command window
- is active.
-
- * Debugger's Reference Manual, Using the Debugger/Navigating with Menu Keys:
- [HOME] and [END] do not work when you try to navigate within the menus.
-
-
- 4. Miscellaneous
- ----------------
-
- * The extended-DOS version of the debugger (MDB) is a protected-mode program;
- it runs only on an 80386 or 80486 machine under Phar Lap's 386|DOS-
- Extender. To execute MDB, you must have version 4.0 or later of Phar Lap's
- RUN386.EXE available via your PATH environment variable. You must use the
- Windows version of the debugger (MDBW) to debug Windows 3.0 applications.
-
- * MDB.CNF has been modified to get around the DOS 128-character command-line
- limit, as follows: debugger command-line options are written to temporary
- file MDB.ARG; this file is created in your current directory, and is
- deleted when you exit from the debugger.
-
- * Remote debugging has been tested and works with Phar Lap's 386|DOS-Extender
- v2.2d; later versions of the Phar Lap extender have not been tested.
-
-
- 5. AutoCAD Development System
- -----------------------------
-
- * AutoCAD ADS users: please read the ADS appendix in the Debugger User's
- Guide and Reference Manual, and also file README.ADS, for information about
- debugging ADS applications.
-
-
- 6. Known Problems
- ------------------
-
- * To ensure optimal performance of the debugger, an updated copy of Phar Lap
- file DBGLIB.REX is included in this distribution. To make sure this file
- is referenced when linking, your PATH variable must reference the \bin
- directory BEFORE referencing the Phar Lap directory. Version 1.3 of the
- debugger uses Phar Lap v4.0 DBGLIB.REX.
-
- * Graphics debugging is supported only on a VGA monitor with the following
- debugger toggles:
-
- FLIP ON /* This toggle must be on. */
- EGA OFF /* This toggle must be off. */
-
- Graphics debugging on an EGA monitor is possible, but expect inconsistent
- results, because EGA video cards have some read-only registers that the
- debugger cannot restore. Be sure to set the toggles as defined above.
-
- EGA Graphics debugging is supported if you are using the TANDEM feature
- of the debugger.
-
- * DOS program SHARE.EXE may cause a program load to fail.
-
- * The debugger currently does not work with Rational's DOS 4G. However,
- Rational's D32 (debugger) does support High C/C++.
-
- * The debugger currently does not work with ERGO Computing's OS/386.