02.07.2013 Views

Type III C lass A Program

Type III C lass A Program

Type III C lass A Program

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

for this operand. all of core from the starting address to<br />

the end of core is dumped. If an asterisk is not specified<br />

as the third operand. the same procedure is used to<br />

determine the ending address of the dump as that described<br />

above for the starting address. Both addresses must be<br />

within the address range of the user's virtual core, and the<br />

address specified in the third operand must be greater thanthat<br />

specified in the second.<br />

The first three lines of output from the DUMP request give<br />

the contents of general-purpose registers 0-7 and 8-15, and<br />

the floating-point registers 0-6. Thereafter, the contents<br />

of the specified portion of core are given, 32 bytes per<br />

line. The core address of the first byte in the line is<br />

given in the left-most column of the dump and is always an<br />

even doubleword boundary,.<br />

The alphameric interpretation for the 32 bytes is pri,nted to<br />

the right of the specified hexadecimal locations.<br />

Responses:<br />

A carriage return is issued and the keyboard is unlocked to<br />

accept another DEBUG request. The requested information is<br />

printed offline as soon as the printer is available,.<br />

INVALID DEBUG REQUEST<br />

No. two" or more than three operands have been specified in<br />

the DUMP request. Reissue the request,. specifying one or<br />

three operands.<br />

INVALID ARGUMENT<br />

This message is given if the address specified by the third<br />

operand is less than that specified by the second operand or<br />

the second and/or third operands cannot be located in the<br />

DEBUG symbol table and are not valid hexadecimal numbers.<br />

If either operand is intended to be a symbol, a DEF request<br />

must previously have been issued for that symbol: if not.<br />

the operand must specify a valid hexadecimal core location.<br />

INVALID CORE-ADDRESS<br />

The hexadecimal number specified in the second or third<br />

operand" when added to the current origin. is greater than<br />

the user's virtual core size. If the current origin value<br />

is unknown i , reset it to the desired value by issuing ORIGIN<br />

and reissue the DUMP request.<br />

Example:<br />

DUMP NEUC 0000 05FO<br />

The contents of core from locations 0000 to 05FO(each plus<br />

the current origin) are printed on the offline printer and<br />

identified by the heading NEUC. See Figure 19 for a sample<br />

of this output, where the origin value is o.<br />

DEBUG - DUMP 233

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!