Where should the type information be 346
debugging, consoles. a non-trivial level
It was a wonderful invention on TOPS-10. It could be used by a user or by somebody debugging the monitor. The following is the description in a commands booklet and may not be 100% correct; ISTR being able to set a mask but that could be a figment of a short-circuit.
The -10 monitors both had a crash routine that would take a snapshot of the system and stop or continue the system.
SET BREAK AT addr ON condition AFTER n
Sets address break locations in programs according to specified conditions. AT, ON, and AFTER are optional portions of the command line. AFTER n indicates the number of tiems the sequence is to be followed before the break occurs. You can use the folllowing line to remove a condition:
SET BREAK NO condition
And you can use the following line to remove all conditions:
SET BREAK NONE
The following is a list of the possible conditions:
ALL
Breaks if the program reads, writes, or fetches the address.
EXECUTE
Ah, that's the magic incantation...thanks :-). Can you create a programmable logic analyzer? address). This is a start. Now if you can do something with a bit mask and trapping. We did in...
Breaks if the program fetches an instruction from the address.
MUUO
so a VM supervisor next to the hardware has to emulate a TLB for the virtual machines that it manages; this could be by having special unique address space...
Breaks if the operating system reads, writes, or fetches the address.
READ
Breaks if the contents of the address are read by the program.
WRITE
Breaks if the program writes into the address.
BAH
Subtract a hundred and four for e-mail.
Where should the type information be 347
Alt Folklore Computers from Newsgroups