PDP-10 Archive: swskit-documentation/front-end-ddt.fnc from AP-4178E-RM

Trailing-Edge - PDP-10 Archives - AP-4178E-RM - swskit-documentation/front-end-ddt.fnc
There are no other files named front-end-ddt.fnc in the archive.
.FLAG CAPITALIZE
.LOWER CASE
.NOFILL
.NOJUST
					^Document:	<FEDDT.^F^N^C
.BLANK
					^Date: 23 ^APRIL 1976
.BLANK
					^Project: ^FRONT ^END ^SUPPORT
.BLANK
					^Charge ^Number:
.BLANK
					^Product ^I^D:
.BLANK
.BLANK
	     ^Functional ^Specification for <FEDDT	
.BLANK
.BLANK
.BLANK
.BLANK
.BLANK
.BLANK
.BLANK
^Issued ^By:				(^Developer)
.BLANK
					(^Supervisor)
.BLANK
^Approved ^By:				(^Funding ^Manager)
.BLANK
					(^Development ^Manager)
.BLANK
^Reviewed ^By:
.PAGE
.BLANK
.FILL
.NOJUST
1.0	^Product ^Overview
.BLANK
1.1	^Product ^Description
.BLANK
<FEDDT IS A SYMBOLIC DEBUGGER FOR THE <TOPS-20 FRONT
END COMPUTER. ^IT RUNS UNDER TIMESHARING, AND ALLOWS
THE USER TO READ AND PRINT SELECTED PORTIONS OF FRONT
END CRASHES.
.BLANK
.BLANK
1.2	^Markets
.BLANK
<FEDDT IS INTENDED AS A SUPPORT AND DEVELOPMENT TOOL
FOR ^DIGITAL ^EQUIPMENT ^CORPORATION. ^DUE TO THE
PROPRIETARY NATURE OF FRONT END SOFTWARE, <FEDDT
IS NOT INTENDED FOR SALE OR RELEASE TO CUSTOMERS.
.BLANK
.BLANK
1.3	^Competitive ^Analysis
.BLANK
^NOT APPLICABLE
.BLANK
.BLANK
1.4	^Product ^Audience
.BLANK
<FEDDT IS INTENDED FOR USE BY <DEC
SOFTWARE SPECIALISTS OR SOFTWARE
DEVELOPMENT PERSONNEL.
.BLANK
.BLANK
2.0	^Product ^Goals
.BLANK
2.1	<FEDDT WILL BE ABLE TO READ CRASH DUMPS PRODUCED
BY THE ^D^E^CSYSTEM-20 OF THE FRONT END <PDP11.
.BLANK
.BLANK
2.2	<FEDDT WILL ALLOW THE USER TO EXAMINE ARBITRARY
LOCATIONS IN THE DUMP.
.BLANK
.BLANK
2.3	<FEDDT WILL ALLOW THE USER TO SELECT OCTAL, SYMBOLIC,
OR <PDP-11 INSTRUCTIONS AS THE OUTPUT FORMAT FOR
DATA.
.BLANK
2.4	<FEDDT WILL ALLOW THE USER TO DEFINE ADDRESSES
SYMBOLICALLY, OR TO READ IN SYMBOL TABLES PRODUCED
BY <RSX20F <TKB, <LNKX11, OR <MACY11.
.BLANK
2.5	<FEDDT WILL ALLOW THE USER TO DIVERT OUTPUT TO
ANY <TOPS-20 DEVICE, AND TO DUMP SELECTED REGIONS
OF THE FILE (OR THE ENTIRE FILE) IN ANY OF THE MODES
DEFINED IN SECTION 1.2.3
.BLANK
2.6	<FEDDT WILL ALLOW THE USER TO COMPARE SELECTED
PORTIONS OF TWO BINARY DUMPS, AND OUTPUT THE
DIFFERENCES TO ANY <TOPS-20 OUTPUT DEVICE.
.BLANK
2.7	^IT IS AN EXPLICIT NON-GOAL OF VERSION 1 OF
<FEDDT TO BE RUN ON 1080 OR ANY NON <TOPS20
SYSTEM.
.BLANK
3.0	^Functional ^Definition
.BLANK
3.1	^Operational description
.BLANK
<FEDDT WILL BE RUN AS A JOB ON THE <TOPS-20
OPERATING SYSTEM. ^NO SPECIAL PRIVILEGES ARE
REQUIRED, EXCEPT ACCESS TO A FRONT END DUMP
FILE.
.BLANK
3.2	^Restrictions
.BLANK
^NONE
.BLANK
4.0	^Compatibility
.BLANK
4.1	^D^E^C ^Products
.BLANK
<FEDDT IS BUILT FROM ^DAVE ^MC^LURE'S <DDT-11. ^IT 
IS MODELED AFTER <PDP-10 SYMBOLIC <DDT. ^THE MAIN
DIFFERENCES ARE THAT <FEDDT MANIPULATES <PDP-11
TYPE DATA STRUCTURES, AND CONTAINS <PDP-11 
INSTRUCTIONS AS ITS INITIAL SYMBOL TABLE.
.BLANK
4.2	^D^E^C ^Standards
.BLANK
^TO AS GREAT A DEGREE AS POSSIBLE, <FEDDT WILL
CONFORM TO THE <TOPS-20 CODING STANDARDS.
.BLANK
4.3	^External ^Standards
.BLANK
5.0	^External ^Interactions and ^Impact
.BLANK
5.1	^Users
.BLANK
<FEDDT SHOULD HAVE NO IMPACT ON ^D^E^CSYSTEM-20
USERS, OTHER THAN AS SPECIFIED IN SECTION 4.
.BLANK
5.2	^Software ^Products
.BLANK
5.2.1	^Products ^That ^Use ^This ^Product
.BLANK
<FEDDT IS FOR USE DURING TIMESHARING ON <TOPS-20
SYSTEMS.
.BLANK
5.2.2	^Products ^That ^This ^Product ^Uses
.BLANK
<FEDDT READS THE DUMPS PRODUCED BY <RSX20^F
(MORE SPECIFICALLY, THE BOOTSTRAP <ROM IN THE
FRONT END <PDP-11). ^THESE ARE TRANSMITTED TO
THE <TOPS-20 FILE SYSTEM BY <SETSPD, A JOB RUN
AT SYSTEM STARTUP. <FEDDT ALSO READS SYMBOL
FILES PRODUCED BY <MACY11, <LNKX11, <TKB, AND
<PDP-11 <MACRO.
.BLANK
5.3	^Other ^Systems (^Networks)
.BLANK
<FEDDT DOES NOT CURRENTLY SUPPORT NETWORKS, BUT
HAS BEEN WRITTEN TO ALLOW EXPANSION TO <DCOPS
WHEN <DCOPS IS RELEASED FOR <TOPS-20.
.BLANK
5.4	^Data ^Storage, ^File ^Structures, ^Data ^Formats and
^Retrieval ^Subsystem
.BLANK
5.4.1	^DUMP ^FILE ^FORMAT
.BLANK
<FEDDT EXPECTS THE DUMP FILE OF THE FRONT END
TO BE A BINARY FILE. ^EACH 36 BIT WORD IS
INTERPRETED AS TWO 18 BIT BYTES, EACH CONTAINING
ONE 16 BIT <PDP-11 WORD:
.BLANK
.NOFILL
------------------------------------------------
!Z!Z! 16 BITS OF DATA  !Z!Z! 16 BITS OF DATA   !
------------------------------------------------
^NOTE-- Z = MUST BE ZERO
.BLANK
.FILL
.NOJUST
.BLANK
5.4.2	^INTERNAL ^REPRESENTATION OF ^DATA
.BLANK
<FEDDT STORES DATA IN <KL10 CORE IN
EXACTLY THE SAME WAY IN WHICH IT IS
STORED ON THE DISK.
.BLANK
5.4.3	^SYMBOL ^FILE ^FORMATS
.BLANK
^SEVERAL TYPES OF SYMBOL TABLE FILES ARE
ALLOWED. ^IF THE EXTENSION IS .^M^A^P, THE
FILE IS ASSUMED TO BE EITHER A <LNKX11 MAP,
OR A <TKB MAP. ^SYMBOLS ARE RECOGNIZED AS
A SYMBOL, FOLLWED BY A SPACE OR TAB, FOLLWED BY
A STRING OF SIX OR FEWER LETTERS, PRECEEDED
BY AT LEAST ONE SPACE OR TAB, FOLLOWED BY AT LEAST
ONE SPACE OR TAB, FOLLOWED BY A NUMBER.
^THE FIRST SYMBOL IS LOCATED BY SEARCHING FOR
AT LEAST TWO LINE FEEDS FOLLWED BY A STRING AS
SPECIFIED ABOVE.
.BLANK
^IF THE EXTENSION IS OTHER THAN .^M^A^P, <FEDDT
SEARCHES FOR SYMBOLS BY LOOKING FOR NUMBERS
FOLLOWED BY AN EQUAL SIGN, A PERCENT SIGN 
(WHICH INDICATES REGISTER DEFINITION), OR THE
LETTER "R" (INDICATING A RELOCATABLE SYMBOL).
^IF ONE OF THESE IS FOUND, THE LAST SIXBIT
QUANTITY READ BEFORE THE NUMBER IS ASSUMED TO
BE THE SYMBOL NAME. ^IF A SYMBOL IS RELOCATABLE,
<FEDDT WILL IGNORE IT UNLESS THE USER HAS ISSUED
A $^P COMMAND TO ENABLE LOADING OF RELOCATABLE
SYMBOLS.
.BLANK
5.4.4	^INTERNAL ^REPRESENTATION OF ^SYMBOLS
.BLANK
^PRE-DEFINED SYMBOLS (SUCH AS INSTRUCTION
MNEMONICS) ARE ASSEMBLED WITH THE PROGRAM,
AND HAVE THE FORMAT:
.BLANK
.NOFILL
-------------------------------------------------
!	<SIXBIT SYMBOL NAME			!
-------------------------------------------------
!	FLAGS		!	VALUE		!
-------------------------------------------------
!	POINTER TO NEXT SYMBOL BLOCK		!
-------------------------------------------------
.FILL
.NOJUST
.BLANK
5.5	^Protocols
.BLANK
^THIS VERSION OF <FEDDT HAS NO PROTOCOL CONVENTIONS.
.BLANK
6.0	^Reliability/^Availability/^Serviceability (^R^A^S)
.BLANK
<FEDDT WILL BE DISTRIBUTED TO SOFTWARE SPECIALISTS
AS PART OF THE FRONT END SUPPORT KIT. ^IT WILL NOT
BE AVAILABLE FOR CUSTOMER USE, AND WILL NOT ITSELF
BE A SUPPORTED PRODUCT.
.BLANK
7.0	^Packaging and ^System ^Generation
.BLANK
7.1	^Distribution ^Media
.BLANK
<FEDDT WILL BE DISTRIBUTED ON MAGNETIC TAPE AS
PART OF THE FRONT END SUPPORT KIT FOR SOFTWARE
SPECIALISTS (THIS IS PART OF A LARGER ^SOFTWARE
^SUPPORT ^KIT FOR THE ^D^E^CSYSTEM-20).
.BLANK
7.2	^Sysgen ^Procedures
.BLANK
<FEDDT IS ASSEMBLED USING A COMMAND FILE (<FEDDT.^C^T^L),
WHICH IS SUBMITTED TO THE <BATCH SYSTEM USING THE
<SUBMIT COMMAND.
.BLANK
8.0	^Documentation
.BLANK
8.1	^PROJECT ^PLAN FOR ^FRONT ^END <DDT
.BLANK
8.2	^THIS ^FUNCTIONAL ^SPECIFICATION
.BLANK
8.3	<FEDDT ^USERS ^MANUAL (INCLUDED AS AN APPENDIX)
.BLANK
9.0	^References
.BLANK
^THE CODING STANDARDS FOR <TOPS-20 ARE DETAILED
IN THE ^D^E^CSYSTEM-20 ^UPDATE ^COURSE ^STUDENT
^GUIDE, ^BOOK 2, ^MODULE 2.
.BLANK
10.0	^Appendix
.BLANK
^THE APPENDIX TO THIS ^FUNCTIONAL ^SPECIFICATION
IS THE ^USERS ^MANUAL FOR <FEDDT.
.BLANK


.FILL
.APPENDIX <FEDDT ^USER ^MANUAL
.PAGE
.FLAG CAPITALIZE
.TITLE <FEDDT ^FRONT ^END ^DEBUGGER
.CENTER
^^FEDDT - TOPS-20 FRONT END DEBUGGER\\
.BLANK
^THE INFORMATION IN THIS DOCUMENT IS SUBJECT 
TO CHANGE WITHOUT NOTICE AND SHOULD NOT BE CONSTRUED AS 
A COMMITMENT BY ^DIGITAL ^EQUIPMENT ^CORPORATION.
.BLANK
^ACTUAL DISTRIBUTION OF THE SOFTWARE DESCRIBED IN THIS 
SPECIFICATION WILL BE SUBJECT TO TERMS AND CONDITIONS 
TO BE ANNOUNCED AT SOME FUTURE DATE BY 
^DIGITAL ^EQUIPMENT ^CORPORATION.
.BLANK
^^DEC\\ ASSUMES NO RESPONSIBILITY FOR THE USE OR 
RELIABILITY OF ITS SOFTWARE ON EQUIPMENT WHICH IS NOT 
SUPPLIED BY ^^DEC\\.
.PAGE
.PAGE
.BLANK
.CENTER
<FEDDT - <TOPS-20 ^FRONT ^END ^DEBUGGER
.BLANK
.BLANK
<FEDDT IS A VERSION OF ^DAVE ^MCCLURE'S ^^DDT-11\\ 
WHICH HAS BEEN ADAPTED FOR USE ON <TOPS-20. 
<FEDDT PROVIDES A TOOL FOR SYMBOLIC DEBUGGING
OF DUMPS TAKEN OF FRONT END CRASHES ON A
^D^E^CSYSTEM-20 (<RSX20F), OR FOR SYMBOLICALLY EXAMINING AND
DEPOSITING IN THE PHYSICAL FRONT END MEMORY,
USING THE <DTE-20 AND THE PRIMARY PROTOCOL EXAMINE
AND DEPOSIT FUNCTIONS. ^NUMERIC EXPRESSIONS ARE PARSED 
STRICTLY LEFT TO RIGHT WITHOUT PRECEDENCE. ^THIS IMPLIES THAT
AN EXPRESSION SUCH AS 100+20*2 = 120*2 = 240, RATHER
THAN THE ERHAPS TO BE EXPECTED 140.

.PARA 0
<FEDDT CAN TYPE ^P^D^P-11 ADDRESSES AS INSTRUCTIONS, 
NUMBERS IN A GIVEN RADIX, OR BYTES OF A GIVEN 
SIZE. ^IT HAS THE CAPABILITY FOR ACCEPTING USER 
DEFINED SYMBOLS, EITHER READ FROM A .MAP OR .CRF 
LISTING (WITH A $$^Y COMMAND), OR DEFINED AT THE 
TERMINAL (USING A COLON COMMAND). ^IN ADDITION, 
<FEDDT HAS AN INITIAL SYMBOL TABLE OF ALL <PDP-11/40 
INSTRUCTIONS.
.PARA
<FEDDT USUALLY READS A BINARY DUMP FILE OF <PDP-11 CORE. ^THIS 
FILE NORMALLY COMES ACROSS THE <DTE-20 WHEN <SETSPD RUNS AFTER 
THE FRONT END CRASHES, AND IS NAMED _<<SYSTEM><0DUMP11.<BIN. 
^THE USER SHOULD TRANSFER THIS FILE