DOCUMENTATION CHANGES FOR: RDOS/DOS DEBUGGING UTILITIES PART NUMBER 069-400020-01 THIS FILE (FILENAME 069400020.01) CONTAINS INFORMATION THAT AFFECTS THE FOLLOWING PAGES OF YOUR MANUAL: *3 *44 *5 *45 *6 *46 *7 *47 *33 *49 *35 *50 *37 *70 *38 *39 *40 *42 *43 THIS SECOND REVISION OF 069400020.01 WAS UPDATED ON JANUARY 20, 1989. ITEMS APPEARING HERE SINCE THE LAST REVISION ARE EASY TO IDENTIFY: IN THE LIST ABOVE, ASTERISKS (*) MARK PAGES WITH CHANGES PRINTED IN THIS FILE FOR THE FIRST TIME. AND, IN THE MARGIN OF PAGES THAT FOLLOW, CHANGE BARS (|) MARK THE NEW MATERIAL. FOR EXAMPLE, THIS REVISION OF 069400020.01 CONTAINS A CHANGE TO PAGE 3 OF ITS PARENT MANUAL. YOU ARE SEEING THIS CHANGE FOR THE FIRST TIME, AND BARS APPEAR NEXT TO IT. TO KEEP YOUR MANUAL CURRENT, YOU SHOULD DO EITHER OF THE FOLLOWING: O MARK THE AFFECTED PAGES OF YOUR MANUAL SO THAT YOU WILL KNOW TO REFER TO THIS FILE FOR ADDITIONAL INFORMATION. O PRINT THIS FILE, PUNCH HOLES TO FIT YOUR BINDER, AND INSERT THE PAGES INTO YOUR MANUAL. COPYRIGHT (C) DATA GENERAL CORPORATION, 1984-1989 ALL RIGHTS RESERVED LICENSED MATERIAL - PROPERTY OF DATA GENERAL CORPORATION RDOS/DOS DEBUGGING UTILITIES, 069-400020-01 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 3 | DSKED SUPPORTS QUITE A FEW DISKS THAT ARE NOT MENTIONED ON PAGE 3. | THESE ARE LISTED BELOW UNDER THE HEADINGS "NOVA AND ECLIPSE DISKS," | "MICRONOVA AND MICROECLIPSE DISKS," AND "MV/FAMILY DISKS." | | NOVA AND ECLIPSE DISKS | | 4514 5.25" 48 TPI DISKETTE .37 MB | 6030 8" SINGLE-DENSITY DISKETTE .35 MB | 6038 8" SINGLE-DENSITY DISKETTE .35 MB | 6236 14" SEALED MOVING HEAD DISK 354 MB | 6239 14" SEALED MOVING HEAD DISK 592 MB | 6357 14" SEALED MOVING HEAD DISK 862 MB | | MICRONOVA AND MICROECLIPSE DISKS | | 4513 5.25" 48 TPI DISKETTE .37 MB | 6102 14" SEALED MOVING HEAD DISK 12 MB | 6224 8" SEALED MOVING HEAD DISK ON BMC 15 MB | 6268 5.25" 48 TPI DISKETTE .37 MB | 6271 5.25" SEALED MOVING HEAD DISK 15 MB | 6280 14" SEALED MOVING HEAD DISK ON BMC 50 MB | 6301 5.25" SEALED MOVING HEAD DISK 38 MB | 6336 5.25" SEALED MOVING HEAD DISK 70 MB | 6506 3.5" SEALED MOVING HEAD DISK 20 MB | 6507 5.25" SEALED MOVING HEAD DISK 40 MB | 6508 5.25" SEALED MOVING HEAD DISK 70 MB | 6509 5.25" SEALED MOVING HEAD DISK 160 MB | 6510 5.25" 48 TPI DISKETTE DRIVE .37 MB | 6511 5.25" 96 TPI DISKETTE DRIVE .73 MB | | MV/FAMILY DISKS | | 6297 5.25" SEALED MOVING HEAD DISK 40 MB | 6309 5.25" 96 TPI DISKETTE .73 MB | 6310 5.25" SEALED MOVING HEAD DISK 38 MB | 6328 5.25" SEALED MOVING HEAD DISK 70 MB | 6329 5.25" SEALED MOVING HEAD DISK 120 MB | 6363 5.25" SEALED MOVING HEAD DISK 160 MB | 6446 5.25" SEALED MOVING HEAD DISK 230 MB | 6491 5.25" SEALED MOVING HEAD DISK 320 MB RDOS/DOS DEBUGGING UTILITIES, 069-400020-01 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 | CHANGE THE BEGINNING OF THE SECOND PARAGRAPH IN THE SECTION | "INVOKING DSKED" TO READ AS FOLLOWS: | | THE FIRST MESSAGES FROM DSKED ARE: | | DISK EDITOR - REVISION NN.NN | | DISK DRIVE MODEL NUMBER? | | THE VALID RESPONSE IS THE DISK DRIVE MODEL NUMBER AND A CAR- | RIAGE RETURN () OR NEW LINE. | | YOU ALSO MAY USE A NEW LINE AFTER THE DISK UNIT NAME YOU SUPPLY IN | RESPONSE TO THE DISK UNIT? QUESTION. IN ADDITION, THE EXAMPLES ON PAGE 3 IMPLY THAT YOU MUST TYPE YOUR INPUT TO THE PROGRAM IN UPPERCASE LETTERS AND THAT DSKED PRINTS ITS MESSAGES IN UPPERCASE. NOW, DSKED ACCEPTS UPPERCASE OR LOWERCASE INPUT. THUS, THE DISK-UNIT ENTRIES DZ0 AND DZ0, OR THE COMMANDS ESC-M AND ESC-M, WILL FUNCTION IDENTICALLY. ALSO, THE UTILITY USES LOWERCASE CHARACTERS IN MANY OF ITS PROMPTS. RDOS/DOS DEBUGGING UTILITIES, 069-400020-01 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 5 | THERE ARE SEVERAL ERRORS IN TABLE 2.1. THESE ARE LISTED BELOW: | | 1) THE THIRD DISPLAY COMMAND, THE LEFTARROW, SHOULD BE AN | UNDERSCORE. | | 2) THE SEVENTH DISPLAY COMMAND, THE DOWNARROW, SHOULD BE A NEW | LINE. | | 3) THE EIGHTH DISPLAY COMMAND, THE UPARROW, SHOULD BE A | SHIFT-6. RDOS/DOS DEBUGGING UTILITIES, 069-400020-01 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 6 | IN TABLES 2.3 AND 2.4, ALL THE LEFTARROWS SHOULD BE UNDERSCORES. RDOS/DOS DEBUGGING UTILITIES, 069-400020-01 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 7 | THERE ARE TWO ERRORS ON PAGE 7. FIRST, NEAR THE BOTTOM OF THE | FIRST COLUMN, THE MANUAL STATES THAT THE CODE YOU USE TO SUPPRESS | LEADING ZEROS IS 4000; THE CORRECT CODE IS 40000. SECOND, AROUND | THE MIDDLE OF THE SECOND COLUMN, THERE IS AN EXAMPLE THAT READS | | .%N 000010 40000+10 | | THIS LINE SHOULD READ | | .$N 000010 40000+10 RDOS/DOS DEBUGGING UTILITIES, 069-400020-01 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 33 | IN THE FOURTH PARAGRAPH IN THE LEFT COLUMN, THE MANUAL STATES THAT | "THE COMMAND LANGUAGES WITHIN THE VERSIONS OF THE GENERIC TYPE ARE | IDENTICAL . . . ." THIS IS NO LONGER TRUE, HOWEVER. THERE ARE SOME | SIGNIFICANT DIFFERENCES BETWEEN ADEB AND THE OTHER DEBUG VERSIONS | AND BETWEEN AIDEB AND THE OTHER IDEB VERSIONS. THESE DIFFERENCES | ARE EXPLAINED LATER IN THIS UPDATE FILE. RDOS/DOS DEBUGGING UTILITIES, 069-400020-01 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 35 | IN THE SECTION "COMMAND FORMAT," THE MANUAL STATES THAT A SYMBOLIC | DEBUGGING COMMAND HAS THE FORMAT | | [ARGUMENT][$]COMMAND-CODE | | IF A GIVEN COMMAND REQUIRES THAT YOU USE THE SECOND ELEMENT IN THIS | FORMAT ($), YOU SHOULD TYPE IN THE ESC CHARACTER, WHICH IS ECHOED | ON YOUR CONSOLE AS A DOLLAR SIGN. | | ALSO, AT THE BOTTOM OF THE LEFT COLUMN, ADD THE FOLLOWING NOTE: | | NOTE: MOST OF THE DEBUGGERS REQUIRE THAT ALL THE ALPHABETIC | CHARACTERS IN A COMMAND LINE BE UPPERCASE. HOWEVER, | ADEB AND AIDEB RECOGNIZE BOTH UPPERCASE AND LOWERCASE | LETTERS. ALSO, WHILE MOST OF THE DEBUGGERS DO NOT ALLOW | YOU TO DELETE A CHARACTER YOU HAVE ENTERED ON YOUR | COMMAND LINE, ADEB AND AIDEB LET YOU USE THE DEL KEY TO | BACK UP TO THE MOST RECENT DELIMITER, WHERE A DELIMITER | IS ANY NON-ALPHANUMERIC CHARACTER OTHER THAN A PERIOD OR | A BACKSLASH (\). FOR EXAMPLE, LET'S ASSUME YOU HAVE | ENTERED THIS COMMAND LINE: | | START+1024. | | IN ADEB AND AIDEB, YOU CAN DELETE THE CHARACTERS BACK | TO, BUT NOT INCLUDING, THE PLUS SIGN. RDOS/DOS DEBUGGING UTILITIES, 069-400020-01 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 37 | CHANGE THE SECOND PARAGRAPH ON THE PAGE TO READ AS FOLLOWS: | | ONCE YOU HAVE OPENED THE MEMORY LOCATION USING EITHER THE SLASH | (/) OR THE EXCLAMATION POINT, YOU CAN MODIFY THE CONTENTS OF | THE LOCATION AND CLOSE IT OR CLOSE THE LOCATION WITHOUT MAKING | ANY MODIFICATIONS. | | REPLACE THE CURRENT TABLE 8.1 WITH THE FOLLOWING ONE: | | KEY(S) ACTION | ------ ------ | | CLOSES AN OPEN LOCATION. OR IF YOU ARE USING DEBUG | AND HAVE NOT OPENED YOUR CONSOLE IN BINARY MODE, | CLOSES AN OPEN LOCATION AND OPENS THE | SUCCEEDING LOCATION. | | NOTE: IN THE EXAMPLES IN THIS SECTION OF THE MANUAL, | IS USED AS THE SYMBOL FOR CLOSING AN OPEN | LOCATION. | | CLOSES AN OPEN LOCATION AND OPENS THE SUCCEEDING | ONE. OR IF YOU ARE USING DEBUG AND HAVE NOT OPENED | YOUR CONSOLE IN BINARY MODE, SIMPLY CLOSES AN | OPEN LOCATION. | | NOTE: IN THE EXAMPLES IN THIS SECTION OF THE MANUAL | IS USED AS THE SYMBOL FOR CLOSING AN OPEN | LOCATION AND OPENING THE SUCCEEDING ONE. | | SHIFT-6 CLOSES AN OPEN LOCATION AND OPENS THE PRECEDING | LOCATION. | | / CLOSES AN OPEN LOCATION AND OPENS THE LOCATION | SPECIFIED BY THE CONTENTS OF THAT LOCATION. | | REPLACE THE PARAGRAPH FOLLOWING TABLE 8.1 WITH THE FOLLOWING | MATERIAL: | | YOU USE THESE COMMANDS TO OPEN AND CLOSE LOCATIONS IN ALL | VERSIONS OF THE SYMBOLIC DEBUGGER. IN ADDITION, ADEB AND AIDEB | CLOSE AN OPEN LOCATION WHENEVER YOU PRESS THE ESC KEY; | THEREFORE, IN THESE VERSIONS OF THE DEBUGGER, IT IS NOT NECES- | SARY TO CLOSE AN OPEN LOCATION BY PRESSING THE CARRIAGE RETURN | OR NEW LINE KEY BEFORE YOU ENTER A NEW COMMAND. RDOS/DOS DEBUGGING UTILITIES, 069-400020-01 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 | A FEW EXAMPLES OF THE COMMANDS FOLLOW. | | CHANGE THE EXAMPLES THAT BEGIN NEAR THE BOTTOM OF THE LEFT COLUMN | TO READ AS FOLLOWS: | | START/006011 6017 | | OPENS THE SYMBOLIC LOCATION START, MODIFIES ITS CONTENTS TO | 6017, AND THEN OPENS THE SYMBOLIC LOCATION START-1. | | 762/000000 | | OPENS LOCATION 762, DOES NOT MODIFY ITS CONTENTS, AND THEN | OPENS THE PRECEDING LOCATION, 761. | | +761 177400 | | CLOSES LOCATION 761 AND OPENS THE PREVIOUS ONE, 760. | | +760 177400 | | CLOSES LOCATION 760. | | START/006017 | | OPENS THE SYMBOLIC LOCATION START AND THEN CLOSES THAT LOCATION | AND OPENS THE NEXT. | | START+1 001400 | | CLOSES LOCATION START+1 AND OPENS THE NEXT ONE. | | START+2 006073 | | CLOSES LOCATION START+2 WITHOUT OPENING THE FOLLOWING LOCATION. | | IN THE SECTION "MONITORING SPECIAL REGISTERS," CHANGE THE THIRD | SENTENCE OF THE FIRST PARAGRAPH TO READ THIS WAY: | | YOU NORMALLY CLOSE A SPECIAL REGISTER BY PRESSING THE CARRIAGE | RETURN KEY; HOWEVER, YOU CAN ALSO USE THE SLASH OR EXCLAMATION | POINT WHERE APPROPRIATE. RDOS/DOS DEBUGGING UTILITIES, 069-400020-01 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 38 | REPLACE THE CURRENT SECTION "ACCUMULATORS" WITH THE FOLLOWING | MATERIAL. | | ACCUMULATORS | | THE COMMAND THAT OPENS AN ACCUMULATOR FOR EXAMINATION OR | MODIFICATION IS USED IN ALL VERSIONS OF THE DEBUGGER. THE | COMMAND FORMAT IS | | N$A | | THE ARGUMENT N IS THE NUMBER OF THE ACCUMULATOR YOU WANT TO | WORK WITH AND CAN RANGE FROM 0 TO 3. | | TO EXAMINE ALL FOUR ACCUMULATORS, ENTER THE FOLLOWING COMMAND: | | $A | | THE UTILITY PERFORMS A CARRIAGE RETURN AND PRINTS THE NUMBER | AND CONTENTS OF EACH ACCUMULATOR. | | NOTE: IF YOU USE THE COMMAND $A WHILE RUNNING ADEB OR AIDEB, | THE UTILITY DISPLAYS NOT ONLY THE VALUES OF THE | ACCUMULATORS, BUT THE VALUES OF THE STACK POINTER AND | FRAME POINTER AS WELL. MOREOVER, YOU CAN USE THE | COMMAND 4$A TO DISPLAY ONLY THE VALUE OF THE STACK | POINTER AND THE COMMAND 5$A TO DISPLAY THE VALUE OF THE | FRAME POINTER. | | REPLACE THE SECTION ENTITLED "FLOATING-POINT ACCUMULATORS" WITH THE | FOLLOWING MATERIAL. | | YOU CAN EXAMINE THE CONTENTS OF THE FOUR FLOATING-POINT ACCUMU- | LATORS AND THE FLOATING-POINT STATUS REGISTER BY USING THE | COMMAND | | $F | | THE DEBUGGER PERFORMS A CARRIAGE RETURN/LINE FEED AND PRINTS | THE NUMBER AND CONTENTS OF EACH FLOATING-POINT ACCUMULATOR. | THE VALUE FOLLOWING THE NUMBER 4 IS THE VALUE OF THE 32-BIT | FLOATING-POINT STATUS REGISTER. RDOS/DOS DEBUGGING UTILITIES, 069-400020-01 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 | REPLACE THE SECOND HALF OF THE RIGHT COLUMN (STARTING WITH THE | SENTENCE THAT BEGINS "AS THE SEARCH PROCEEDS . . .") WITH THE | FOLLOWING MATERIAL: | | AS THE SEARCH PROCEEDS, THE PROGRAM COMPARES THE LOGICAL AND OF | THE DATA AT EACH LOCATION AND A MASK REGISTER (DESCRIBED BELOW) | WITH THE CONTENTS OF THE WORD REGISTER. IF THE RESULTS OF THE | AND OPERATION AND THE CONTENTS OF THE WORD REGISTER MATCH, THE | DEBUGGER PRINTS THE DATA AND ITS LOCATION. BY DEFAULT, THE | WORD REGISTER CONTAINS 0. | | YOU CAN SET THE MASK REGISTER WHEN YOU WISH TO MASK THE CON- | TENTS OF CERTAIN BIT POSITIONS IN EACH MEMORY LOCATION DURING | THE SEARCH. THE COMMAND THAT ALLOWS YOU TO DO THIS IS | | $M | | WHEN YOU DO NOT WANT MASKING, SET THE MASK REGISTER TO -1 (ALL | ONES). IF YOU WANT TO MASK CERTAIN BIT POSITIONS, SET THOSE | POSITIONS TO 0 AND SET THE UNMASKED POSITIONS TO 1. AS MEN- | TIONED ABOVE, THE SYSTEM CALCULATES THE LOGICAL AND OF THE MASK | REGISTER AND A MEMORY LOCATION, AND THEN COMPARES THE RESULT | WITH THE CONTENTS OF THE WORD REGISTER. IF THE TWO MATCH, THE | ORIGINAL MEMORY LOCATION AND ITS ORIGINAL VALUE ARE PRINTED. | BY DEFAULT, THE MASK REGISTER IS SET TO 0 (ALL BIT POSITIONS | MASKED). | | THE FOLLOWING EXAMPLE SHOWS HOW EACH COMMAND OPERATES: | | $W 000000 15000 | $W 015000 | $M 000000 177700 RDOS/DOS DEBUGGING UTILITIES, 069-400020-01 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 39 | CHANGE THE EXAMPLE NEAR THE BOTTOM OF THE LEFT COLUMN TO READ AS | FOLLOWS: | | $Y 000402 | 402/060351 | USTAD+3 060233 | USTAD+4 060352 | USTAD+5 050653 | USTAD+6 050751 | USTAD+7 060352 | USTAD+10 000000 | USTAD+11 177777 | | REPLACE THE SECTION ENTITLED "SEARCH/PUNCH REGISTER" WITH THE | FOLLOWING INFORMATION: | | SEARCH-OUTPUT REGISTER (IDEB ONLY) | | BIT 15 OF THE SEARCH-OUTPUT REGISTER SPECIFIES THE OUTPUT | DEVICE TO BE USED WHEN YOU PRINT MEMORY SEARCH RESULTS. WHEN | BIT 15 IS SET TO 0 (THE DEFAULT SETTING), THE SEARCH RESULTS | ARE PRINTED AT YOUR CONSOLE. TO PRINT THE SEARCH RESULTS ON | YOUR PRINTER (DEVICE CODE 17), YOU MUST SET BIT 15 TO 1. YOU | CAN OPEN THE REGISTER WITH THE COMMAND | | $H | | FOR EXAMPLE, THE COMMAND | | $H 000000 1 | | OPENS THE SEARCH-OUTPUT REGISTER AND SETS BIT 15 TO 1. ANY | SEARCH OUTPUT WILL NOW BE DIRECTED TO YOUR PRINTER (DEVICE CODE | 17). | | REPLACE THE SECTION CALLED "INTERRUPT REGISTER" WITH THE FOLLOWING | MATERIAL: | | INTERRUPT REGISTER (IDEB ONLY) | | THE INTERRUPT REGISTER ALLOWS YOU TO DO TWO THINGS: TO DETER- | MINE WHETHER INTERRUPTS WERE ENABLED WHEN YOU ENTERED THE | DEBUGGER AND TO DICTATE WHETHER INTERRUPTS WILL BE ENABLED WHEN | YOU LEAVE THE DEBUGGER. RDOS/DOS DEBUGGING UTILITIES, 069-400020-01 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 | TO PERFORM THE FIRST OF THESE TASKS, ENTER THE COMMAND | | $I | | IF THE REGISTER IS SET TO -2 (177776), THEN INTERRUPTS WERE | ENABLED WHEN YOU STARTED THE DEBUGGER; IF THE REGISTER IS SET | TO -1 (177777), THEY WERE DISABLED. | | SIMILARLY, IF YOU SET THE VALUE OF THE INTERRUPT REGISTER TO -2 | BEFORE YOU LEAVE THE DEBUGGER, INTERRUPTS WILL BE ENABLED WHEN | YOU LEAVE. IF YOU SET THE REGISTER TO -1, INTERRUPTS WILL BE | DISABLED. | | NOTE: IN IDEB UNDER RDOS MAPPING, THE INTERRUPTS NECESSARY FOR | MAPPING ARE NEVER DISABLED. | | DELETE THE SECTION ENTITLED "TASK CONTROL BLOCK REGISTER." RDOS/DOS DEBUGGING UTILITIES, 069-400020-01 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 40 | REPLACE THE SECOND HALF OF THE SECTION "CONSOLE INPUT DONE | REGISTER" (STARTING WITH THE SENTENCE THAT BEGINS "IN THE FOLLOWING | EXAMPLE . . .") WITH THE FOLLOWING MATERIAL: | | GIVEN THE FOLLOWING EXAMPLE, ASSUME THAT A BREAKPOINT HAS BEEN | SET AT A+2: | | A: SKPDN TTI | JMP .-1 | DIAC 0,TTI | | CONTROL WILL BE PASSED TO THE DEBUGGER WHILE CONSOLE INPUT IS | STILL OUTSTANDING. THEREFORE, IF YOU EXAMINE THE CONTENTS OF | THE CONSOLE INPUT DONE REGISTER WHILE STOPPED AT THIS | BREAKPOINT, YOU WILL SEE THAT BIT 0 OF THE REGISTER HAS BEEN | SET TO 1. | | $T 100000 | | REPLACE THE SECOND HALF OF THE SECTION "CARRY AND CONSOLE OUTPUT | DONE REGISTER" (STARTING WITH THE SENTENCE THAT BEGINS "IN THE | FOLLOWING EXAMPLE . . .") WITH THE FOLLOWING MATERIAL: | | ASSUME THAT YOUR PROGRAM IS ABOUT TO EXECUTE THE FOLLOWING | CODE: | | B: ADCO 0,0 | DOAS 0,TTO | SKPDN TTO | JMP .-1 | | IF YOU HAVE A BREAKPOINT SET AT B+3 AND CONTROL PASSES TO THE | DEBUGGER WHILE THE CARRY BIT IS SET AND CONSOLE OUTPUT IS STILL | OUTSTANDING, USING THE $C COMMAND WILL YIELD THESE RESULTS: | | $C 100001 | | REPLACE THE SECTION "STARTING LOCATION REGISTER" WITH THE FOLLOWING | INFORMATION: | | STARTING LOCATION REGISTER | | IF YOU ARE USING A VERSION OF DEBUG, THE STARTING LOCATION | REGISTER CONTAINS THE STARTING ADDRESS OF YOUR PROGRAM. IF YOU | ARE USING A VERSION OF IDEB, THE REGISTER CONTAINS THE ADDRESS | OF THE TASK SCHEDULER. THE CODE THAT FOLLOWS THIS LABEL IS THE RDOS/DOS DEBUGGING UTILITIES, 069-400020-01 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 | CODE THAT EXECUTES YOUR PROGRAM. YOU CAN OPEN THE STARTING | LOCATION REGISTER WITH THE COMMAND | | $L | | IN THE FOLLOWING EXAMPLE, IDEB DISPLAYS THE ADDRESS OF THE TASK | SCHEDULER. (TYPING THE COLON CAUSES THE DEBUGGER TO DISPLAY | THE NAME OF THE SYMBOL ASSOCIATED WITH THE ADDRESS.) | | $L 060215 :TMIN | | REPLACE THE SECTION "EXTENDED SAVE ADDRESS REGISTER" WITH THE | FOLLOWING MATERIAL: | | EXTENDED SAVE ADDRESS REGISTER (DEBUG ONLY) | | WHILE THE DEBUGGER IS INACTIVE, YOUR PROGRAM MAY USE LOCATION | USTSV IN THE USER STATUS TABLE TO STORE THE ADDRESS OF AN | EXTENDED SAVE STATE ROUTINE. WHEN THE DEBUGGER BECOMES ACTIVE, | HOWEVER, IT USES LOCATION USTSV, SO IT STORES THE VALUE THAT | WAS IN USTSV IN THE EXTENDED SAVE ADDRESS REGISTER. YOU CAN | OPEN THIS REGISTER WITH THE COMMAND | | $E RDOS/DOS DEBUGGING UTILITIES, 069-400020-01 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 42 | REPLACE THE FIRST HALF OF THE LEFT COLUMN (UP TO THE BEGINNING OF | THE SECTION "PROGRAM RESTART COMMANDS") WITH THE FOLLOWING | MATERIAL. | | WHEN A BREAKPOINT IS SET, THE BREAK PROCEED COUNTER FOR THAT | BREAKPOINT IS SET BY DEFAULT TO 1, WHICH IS THE NUMBER OF TIMES | THE DEBUGGER MUST SEE THE BREAKPOINT BEFORE IT TAKES CONTROL. | THE COMMAND | | N$Q | | OPENS THE BREAK PROCEED COUNTER OF BREAKPOINT N FOR EXAMINATION | AND POSSIBLE MODIFICATION. THE VARIABLE N REPRESENTS THE | NUMBER OF THE PREVIOUSLY SET BREAKPOINT. YOU CAN MODIFY THE | CONTENTS OF THE BREAK PROCEED COUNTER BY TYPING THE NEW CON- | TENTS IMMEDIATELY FOLLOWING THE PRINTOUT OF THE CURRENT | CONTENTS. IF YOU WERE TO USE THE COMMAND SHOWN BELOW, THE | INSTRUCTION AT BREAKPOINT 7 WOULD EXECUTE ONCE BEFORE THE | DEBUGGER STOPPED THE PROGRAM UPON SEEING THE BREAKPOINT FOR THE | SECOND TIME: | | 7$Q 000001 2 | | THEN THE DEBUGGER WOULD AUTOMATICALLY RESET THE VALUE OF THE | BREAK PROCEED COUNTER TO 1. REPLACE THE FIRST PARAGRAPH IN THE SECTION "PROGRAM RESTART COMMANDS" WITH THE FOLLOWING INFORMATION: THE COMMAND TO START THE PROGRAM INITIALLY IS $R ONCE THE PROGRAM IS RUNNING, HOWEVER, A SECOND $R COMMAND CAUSES THE PROGRAM TO PRINT THE ERROR MESSAGE ?. IN ORDER TO RESTART YOUR CODE AT A GIVEN ADDRESS, USE THE COMMAND ADDR$R | YOUR PROGRAM THEN EXECUTES UNTIL THE DEBUGGER SEES A SECOND | BREAKPOINT, PROVIDED THAT ONE IS SET. AN EXAMPLE OF THE | COMMAND IS | | START+2$R | 6B START+10 | 0 001654 1 000000 2 000000 3 006162 RDOS/DOS DEBUGGING UTILITIES, 069-400020-01 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 | NOTE: IF YOU ARE USING ADEB OR AIDEB AND FORGET THE NUMBER OF | THE BREAKPOINT AT WHICH YOU HAVE STOPPED, YOU CAN REFRESH | YOUR MEMORY BY USING THE COMMAND $U. IN ADDITION, THESE | VERSIONS OF THE DEBUGGER DISPLAY THE VALUES OF THE STACK | POINTER AND THE FRAME POINTER IN ADDITION TO THE VALUES | OF THE ACCUMULATORS. | | DELETE EVERYTHING EXCEPT THE FIRST SENTENCE FROM THE SECTION | "OVERRIDING THE BREAK PROCEED COUNTER." RDOS/DOS DEBUGGING UTILITIES, 069-400020-01 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 43 | THE EXAMPLE AT THE BOTTOM OF THE RIGHT COLUMN SHOULD LOOK THIS WAY: | | $W 000000 6017 | $M 000000 -1 | START, $O, AND N$G COMMANDS. THESE COMMANDS WORK | IN ADEB AND AIDEB ONLY. | | 1) THE COMMAND N$> CAUSES THE DEBUGGER TO DISPLAY TEXT UNTIL | IT SEES A NULL. THE VALUE N IS A BYTE POINTER TO THE | TEXT'S STARTING LOCATION. | | 2) THE $O COMMAND DISPLAYS THE VALUES STORED IN THE CURRENT | STACK FRAME (THAT IS, THE FRAME RESERVED BY THE MOST RECENT | SAVE INSTRUCTION). | | 3) THE COMMAND N$G DISPLAYS THE RETURN ADDRESSES OF SUBROUTI- | NES THAT USE THE SAVE AND RTN INSTRUCTIONS. FOR EXAMPLE, | LET'S ASSUME THAT THE FOLLOWING SITUATION EXISTS. SU- | BROUTINE X1 HAS CALLED SUBROUTINE X2, WHICH, IN TURN, HAS | CALLED SUBROUTINE X3. ALL THREE SUBROUTINES USE SAVE AND | RTN INSTRUCTIONS, AND YOU ARE STOPPED AT A BREAKPOINT IN | X3. THE COMMAND 1$G WILL DISPLAY THE ADDRESS WITHIN X2 TO | WHICH CONTROL WILL RETURN WHEN X3'S RTN INSTRUCTION IS | EXECUTED. THE COMMAND 2$G WILL DISPLAY AN ADDRESS IN | SUBROUTINE X2, FOLLOWED BY AN ADDRESS IN X1. THE COMMAND | 0$G DISPLAYS ALL RETURN ADDRESSES. THE MAXIMUM NUMBER OF | LEVELS YOU CAN TRACE BACK IS 32,768. RDOS/DOS DEBUGGING UTILITIES, 069-400020-01 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 70 | ADD THE FOLLOWING ERROR MESSAGE TO THE SECTION "ENPAT/PATCH ERROR | MESSAGES": | | ERROR: UNEXPECTED END OF LINE ENCOUNTERED. | | THE PATCH UTILITY EXPECTS THE LINES OF A PATCH FILE TO CONTAIN | TRAILING SPACES IN CERTAIN SITUATIONS (MOST NOTABLY IF NO | CONDITIONAL IS SPECIFIED). THE ENPAT UTILITY CREATES A PATCH | FILE OF THE PROPER FORMAT, BUT CERTAIN EDITORS, IF RUN ON A | PATCH FILE, WILL REMOVE TRAILING SPACES. IF PATCH EXPECTS TO | FIND A TRAILING SPACE AND DOES NOT FIND ONE, IT PRINTS THIS | MESSAGE. | --END OF UPDATE FILE--