{ "disks": { "1": { "dirs": [ { "path": "/", "files": [ { "name": "README MDB", "size": 9936, "date": "1991-04-23", "time": "11:11" }, { "name": "LHA EXE", "size": 34283, "date": "1991-07-20", "time": "2:13" }, { "name": "INSTALL1 DAT", "size": 2625, "date": "1991-04-08", "time": "9:16" }, { "name": "INSTALL2 DAT", "size": 2338, "date": "1991-04-08", "time": "9:16" }, { "name": "INSTALL BAT", "size": 2763, "date": "1990-11-25", "time": "19:00" }, { "name": "INSTALLT COM", "size": 20224, "date": "1990-12-04", "time": "10:37" }, { "name": "FIND EXE", "size": 49246, "date": "1990-10-11", "time": "16:08" }, { "name": "CLEANUP BAT", "size": 130, "date": "1990-11-21", "time": "12:36" }, { "name": "MDBSER EXE", "size": 37820, "date": "1990-12-04", "time": "10:53" }, { "name": "MW_DB 1", "size": 49, "date": "1991-04-08", "time": "10:26" }, { "name": "EXAMPLES", "dir": true, "date": "1993-07-16", "time": "10:52" }, { "name": "BIN", "dir": true, "date": "1993-07-16", "time": "10:52" }, { "name": "RUN386 EXE", "size": 145476, "date": "1991-02-11", "time": "17:35" } ] }, { "path": "/EXAMPLES", "files": [ { "name": "MDB_BAD C", "size": 635, "date": "1991-04-08", "time": "10:24" }, { "name": "MDB_GOOD C", "size": 636, "date": "1991-04-08", "time": "10:24" } ] }, { "path": "/BIN", "files": [ { "name": "MDB CNF", "size": 1934, "date": "1991-04-08", "time": "10:24" }, { "name": "MDB BOD", "size": 84078, "date": "1991-04-08", "time": "10:00" }, { "name": "MDB ENV", "size": 1710, "date": "1991-04-08", "time": "15:38" }, { "name": "MDB IDX", "size": 2512, "date": "1991-04-08", "time": "10:00" }, { "name": "MDB TXT", "size": 23871, "date": "1991-04-08", "time": "10:00" }, { "name": "COLOR DB", "size": 32, "date": "1991-04-08", "time": "10:00" }, { "name": "CFIGMDB EXE", "size": 161876, "date": "1991-04-08", "time": "10:00" }, { "name": "MDB EXE", "size": 55392, "date": "1991-04-08", "time": "10:00" }, { "name": "MON EXP", "size": 142333, "date": "1991-04-08", "time": "10:00" }, { "name": "DBGLIB REX", "size": 35032, "date": "1991-03-20", "time": "12:39" }, { "name": "CX EXE", "size": 11582, "date": "1990-08-30", "time": "9:45" }, { "name": "MDB1 CX", "size": 358830, "date": "1991-04-22", "time": "16:33" } ] } ] } }, "desc_file": "README.MDB", "desc_text": " Copyright (C) 1991 MetaWare Incorporated. All Rights Reserved.\r\n\r\n MetaWare Debugger Version 1.13\r\n for Extended DOS 80386/486\r\n April 1991\r\n\r\nTable of Contents\r\n-----------------\r\n\r\n1. Contents of the Distribution\r\n2. Configuring the Debugger\r\n3. Miscellaneous\r\n4. PC-NFS Notes\r\n5. AutoCAD Development System\r\n6. Known Problems\r\n7. Other Problems\r\n\r\n\r\n1. Contents of the Distribution\r\n-------------------------------\r\n\r\n The following files on your mdb distribution disk make up the actual\r\n debugger, mdb examples, and on-line documentation: \r\n\r\n readme.mdb - This file.\r\n bin\\cfigmdb.exe - Debugger user-interface configuration utility.\r\n Operates on the color.db file.\r\n bin\\color.db - Binary file used by the debugger to specify user-\r\n interface colors.\r\n bin\\cx.exe - Executable file compress utility\r\n bin\\dbglib.rex - Phar Lap-provided debugger interface library loaded\r\n dynamically at run time by mdb.exe.\r\n bin\\mdb.bod - Text of the debugger's on-line help.\r\n bin\\mdb.cnf - Debugger driver configuration file.\r\n bin\\mdb.env - Debugger environment file.\r\n bin\\mdb.exe - Debugger driver program.\r\n bin\\mdb.idx - Index file for on-line help.\r\n bin\\mdb.txt - Menu help file used by the debugger.\r\n bin\\mdb1.cx - Compressed debugger executable\r\n bin\\mon.exp - Remote debugging monitor.\r\n examples\\mdb_bad.c - Example program used in debugger tutorial.\r\n examples\\mdb_good.c- Example program used in debugger tutorial.\r\n\r\nYour mdb distribution disk also contains batch files, scripts and\r\nexecutable utility programs that we use during the mdb installation.\r\nThis group of files is listed below:\r\n\r\n bin\\cx.exe \r\n mw_db.1\r\n cleanup.bat\r\n install.bat\r\n installit.com\r\n install1.bat\r\n install2.bat\r\n find.exe\r\n mdbser.exe\r\n\r\n2. Configuring the Debugger\r\n----------------------------\r\n\r\n* Debugger configuration file mdb.env and help files.\r\n\r\n Set environment variable MDBENV to the location of the mdb.env file,\r\n and MDBHELP to the directory in which the help files reside.\r\n\r\n For example:\r\n\r\n set MDBENV=c:\\hc386\\bin\\mdb.env\r\n set MDBHELP=c:\\hc386\\bin\r\n\r\n By default, the debugger looks for its configuration file (mdb.cnf) and its\r\n help files (mdb.txt, mdb.bod, and mdb.idx) in the directory in which the\r\n debugger executable (mdb1.exp) is found.\r\n\r\n* To configure run386 command-line switches for the debugger, you may edit\r\n the mdb.cnf file to set the R386ARGS variable.\r\n\r\n If you hit the MS-DOS command-line limit of 128 characters, you may set\r\n an arbitrary environment variable, say R386, to the desired switches, and\r\n set mdb.cnf's R386ARGS variable to %R386. This will cause run386 to read\r\n the environment variable as part of the command line. See Phar Lap's\r\n run386 documentation for more details.\r\n\r\n* User-Interface Colors\r\n\r\n To change the debugger's user-interface colors, first edit the debugger\r\n configuration file mdb.env in the \\bin directory and set the COLOR variable\r\n to the location of the color file in the \\bin directory. The debugger will\r\n use this color file at start-up. For example:\r\n\r\n COLOR=c:\\hc386\\bin\\color.db\r\n\r\n Then use program cfigmdb to edit color.db and change the colors. Just run\r\n cfigmdb and specify color.db at the Color:Load menu choice.\r\n\r\n* Key Macros\r\n\r\n Function keys F2 through F9, all the Alt-F keys, and all the Ctrl-F keys\r\n can be remapped to any command or macro. Use the Macro:key menu item to\r\n remap any of these keys during a debugging session, or edit file mdb.env to\r\n change the defaults. These key macros can then be invoked from the\r\n debugger command line.\r\n\r\n* Start-Up Macros\r\n\r\n To define a group of macros at debugger start-up, edit the debugger\r\n configuration file mdb.env and set the STARF variable to the location\r\n of your macro file. For example:\r\n\r\n STARF=c:\\hc386\\bin\\start.mac\r\n\r\n\r\n3. Miscellaneous\r\n-----------------\r\n\r\n* The debugger (mdb) is a protected-mode program; it runs only on an 80386\r\n or 80486 machine under Phar Lap's 386|DOS-Extender. To execute the\r\n debugger, you must have version 2.2b or later of run386.exe available via\r\n your PATH environment variable.\r\n\r\n* RELOAD to debug a program again.\r\n\r\n The RELOAD command prepares the currently loaded program to be debugged\r\n again. The debugging environment (breakpoints, watch windows, and so on)\r\n remains unchanged.\r\n\r\n* Integer variables are type long.\r\n\r\n The size of an integer is machine dependent. On the 80386, integers are\r\n four bytes and are mapped to type long by the debugger.\r\n\r\n* Setting the minimum heap size for a program.\r\n\r\n The KEEPHEAP command displays or sets the minimum initial heap size for a\r\n program in pages of 4K bytes. The default is two pages. Normally, a\r\n program grows its heap at run time for dynamic memory allocation. If your\r\n program is built with the assumption that a large heap will be available at\r\n start-up, you may use this command to reserve the amount of memory\r\n necessary for your heap.\r\n\r\n* Expression reevaluation for the EXAMINE command and the Symbol:Examine\r\n window.\r\n\r\n REEVALUATE [ON | OFF] enables or disables expression reevaluation for the\r\n EXAMINE command and the Symbol:Examine window. If neither ON nor OFF is\r\n specified, the current state of reevaluation is displayed.\r\n\r\n If enabled, examined expressions are reevaluated every time the value of an\r\n expression may have changed. Otherwise the expressions are evaluated only\r\n once and the addresses of the resulting lvalues are watched for a change of\r\n contents. By default, REEVALUATE is OFF.\r\n\r\n For example, consider examining the expression foo[i] when i = 3. With\r\n REEVALUATE ON, when i changes, a different element of foo will be\r\n displayed. With REEVALUATE OFF, a change in i will have no effect, and\r\n foo[3] will still be displayed.\r\n\r\n\r\n4. PC-NFS Notes\r\n---------------\r\n\r\n If PC-NFS is installed and there is a network drive on your path, when you\r\n invoke the debugger you will get a message about a network error, such as:\r\n\r\n Unexpected Network Failure\r\n Abort, Retry, Fail?\r\n\r\n At this point, if you type \"f\" the debugger will come up normally. The\r\n problem is that the code in the debugger driver that searches your path for\r\n the DOS extender (run386.exe) provokes an error in PC-NFS. To eliminate\r\n this inconvenience, you can provide the debugger driver with the full\r\n pathname of run386.exe, as follows.\r\n\r\n Edit the file mdb.cnf in the \\bin subdirectory of the directory in which\r\n you installed the debugger. Find the line that reads:\r\n\r\n #exec :run386 ...\r\n\r\n and replace it with a line that uses the full pathname of run386, in place\r\n of \":run386\":\r\n\r\n #exec drive:full\\pathname\\of\\run386 ...\r\n\r\n\r\n5. AutoCAD Development System\r\n-----------------------------\r\n\r\n* AutoCAD ADS users: please read the ADS appendix in the Debugger User's\r\n Guide and Reference Manual.\r\n\r\n\r\n6. Known Problems\r\n------------------\r\n\r\n* To ensure optimal performance of the debugger, an updated copy of Phar Lap\r\n file dbglib.rex is included in this distribution. To make sure this file\r\n is referenced when linking, your PATH variable must reference the \\bin\r\n directory BEFORE referencing the Phar Lap directory.\r\n\r\n* Graphics debugging is supported only on a VGA monitor with the following\r\n debugger toggles:\r\n\r\n FLIP ON /* This toggle must be on. */\r\n EGA OFF /* This toggle must be off. */\r\n\r\n Graphics debugging on an EGA monitor is possible, but expect inconsistent\r\n results, because EGA video cards have some read-only registers that the\r\n debugger cannot restore. Be sure to set the toggles as defined above.\r\n\r\n EGA Graphics debugging is supported if you are using the TANDEM feature\r\n of the debugger.\r\n\r\n* DOS program share.exe may cause a program load to fail.\r\n\r\n* RELOAD might fail under Phar Lap's VMM.\r\n\r\n* Multiple breakpoints at one address are not supported.\r\n\r\n* CALLSTACK cannot display register-based arguments.\r\n\r\n Until we provide extensions to debug records, the debugger's CALLSTACK\r\n command will not be able to locate register parameters.\r\n\r\n* FLIP OFF mode may be confusing when your program requests input.\r\n\r\n If you use FLIP OFF to turn off swapping to the output screen after every\r\n program step, be aware that if your program requests user input you will\r\n not be able to view the output screen to see the prompt.\r\n\r\n* The debugger currently does not work under ERGO Computing's OS/386. We are\r\n working with ERGO Computing to get the needed support added to OS/386.\r\n\r\n* Reloading AutoCAD kills the debugger. AutoCAD resets many interrupt\r\n vectors, and unless it has an opportunity to clean up, the system will be\r\n very confused. \r\n\r\n\r\n7. Other Problems\r\n------------------\r\n\r\nIf you think you have discovered a debugger problem, send a problem report to\r\nMetaWare Technical Support. If possible, please send a test case that\r\ndemonstrates the problem.\r\n\r\nAll problem reports must include your serial number and specify which version\r\nof the compiler you are using. If your sample code exceeds 15 lines, please\r\nsend it by diskette to the address below, or by E-mail to:\r\n\r\n uunet!acad!metaware!tech\r\n -or-\r\n Internet tech@metaware.com\r\n -or-\r\n INTERNET:tech@metaware.com\r\n\r\nMetaWare Technical Support can be reached at (408) 429-6111, 8:00 am to 4:30 pm\r\nMonday through Friday.\r\n\r\n\r\nMetaWare Incorporated\r\n2161 Delaware Avenue\r\nSanta Cruz, CA 95060-5706\r\n(408)429-6382 FAX:(408)429-9273" }