DataMuseum.dk

Presents historical artifacts from the history of:

CR80 Hard and Floppy Disks

This is an automatic "excavation" of a thematic subset of
artifacts from Datamuseum.dk's BitArchive.

See our Wiki for more about CR80 Hard and Floppy Disks

Excavated with: AutoArchaeologist - Free & Open Source Software.


top - download

⟦660592900⟧ TextFile

    Length: 1932 (0x78c)
    Types: TextFile
    Names: »DEBUG.I«

Derivation

└─⟦b8af24a88⟧ Bits:30005796 CR80 Disc Pack ( MINICAMPS )
    └─ ⟦this⟧ »GENS.D!DEBUG.D!DEBUG.I« 

TextFile


%LIST     %LIST     %LIST
"-----------------------------------------------------------------------
"
"  MODULE NAME:           DEBUGGER
"  MODULE ID NMB:         CSS/208
"  MODULE VERSION:        3
"
"-----------------------------------------------------------------------
%NOLIST   %NOLIST   %NOLIST

type
    error_ok_exit = ( err_ex, ok_ex );


import procedure init_MON
"======================="
   ( r0;   "   C K    location of MON program
     r1;   "   C D    level (4 lsb's kept)
     r4;   "   C K    MON number
     r6)   "   C K    link
   :error_ok_exit;

" This procedure introduces a new DAMOS monitor procedure
" to the debugger.
" The error exit is chosen in case of a bad MON number or
" if the monitor entry is already initialzed.
" NOTE: this procedure must be called after init_debugger.



import procedure initialize_emulator
"=================================="
   ( r0;   "  C D    EXR register
     r1;   "  C K    @ process parameter block
     r6)   "  C K    link
   :error_ok_exit;

" This procedure initializes the EXR register
" to the specified values.
" It is further checked that the cur_ptr field of the context
" stack control block is within that part of the data space
" which may be updated by the user.
" The content of the context stack control block must be
" initialized directly by the user.
" NOTE: this procedure must be called after init_debugger.


import procedure init_debugger
"============================"
  (r6); "C D link

"This procedure initializes the debugger.



import var dumpfiletype : record
                             name  : array [0..15] of char;
                             s     : integer;
                             f     : integer;
                          end;
    "this is the debug log file. Filetype is defined in UTH.I

import var ins_count : long;
    "this variable contains the number of instructions executed by the
    "problem modules
"page«ff»