SCCS-vsn: usr.bin/f77/PSD.doc/f77/f77.ms 8.3
SCCS-vsn: usr.bin/f77/PSD.doc/f77io/f77IO.ms 8.3
SCCS-vsn: old/adb/PSD.doc/adb.ms 8.2
.\" %sccs.include.proprietary.roff%
.\"
.\" %sccs.include.proprietary.roff%
.\"
-.\" @(#)adb.ms 8.1 (Berkeley) %G%
+.\" @(#)adb.ms 8.2 (Berkeley) %G%
.\"
.EH 'PSD:11-%''A Tutorial Introduction to ADB'
.OH 'A Tutorial Introduction to ADB''PSD:11-%'
.\"
.EH 'PSD:11-%''A Tutorial Introduction to ADB'
.OH 'A Tutorial Introduction to ADB''PSD:11-%'
request examines the
.ul
corefile.
request examines the
.ul
corefile.
The general form of these requests is:
.P1
address ? format
The general form of these requests is:
.P1
address ? format
and executes the command
\fIcount\fR times.
.PP
and executes the command
\fIcount\fR times.
.PP
The following table illustrates some general ADB command meanings:
.P1
Command Meaning
The following table illustrates some general ADB command meanings:
.P1
Command Meaning
contents of the string pointed to by
.ul
charp.
contents of the string pointed to by
.ul
charp.
This is done by:
.P1
*charp/s
This is done by:
.P1
*charp/s
suppressing the printing of symbolic labels in favor
of octal values.
Note that this is only done for the printing of the data segment.
suppressing the printing of symbolic labels in favor
of octal values.
Note that this is only done for the printing of the data segment.
The request:
.P1
<b,\-1/8ona
The request:
.P1
<b,\-1/8ona
locate,
\fBl\fP or \fBL\fP
request.
locate,
\fBl\fP or \fBL\fP
request.
In general, the request syntax for \fBl\fP and \fBw\fP are similar as follows:
.P1
?l value
In general, the request syntax for \fBl\fP and \fBw\fP are similar as follows:
.P1
?l value
.\"
.\" %sccs.include.proprietary.man%
.\"
.\"
.\" %sccs.include.proprietary.man%
.\"
-.\" @(#)f77.ms 8.2 (Berkeley) %G%
+.\" @(#)f77.ms 8.3 (Berkeley) %G%
(see section 2.14).
(\fB\(mii4\fR is the standard value of this option).
All logical quantities will be short.
(see section 2.14).
(\fB\(mii4\fR is the standard value of this option).
All logical quantities will be short.
.XX \(mi\f3m\f1
Apply the M4 macro preprocessor
to each \s-1EFL\s0 or Ratfor source file
.XX \(mi\f3m\f1
Apply the M4 macro preprocessor
to each \s-1EFL\s0 or Ratfor source file
If the letter is \fBb\fR, the string is binary, and only zeroes and ones are permitted.
If the letter is \fBo\fR, the string is octal, with digits \fB0\(mi7\fR.
If the letter is \fBz\fR or \fBx\fR, the string is hexadecimal, with digits \fB0\(mi9\fR, \fBa\(mif\fR.
If the letter is \fBb\fR, the string is binary, and only zeroes and ones are permitted.
If the letter is \fBo\fR, the string is octal, with digits \fB0\(mi7\fR.
If the letter is \fBz\fR or \fBx\fR, the string is hexadecimal, with digits \fB0\(mi9\fR, \fBa\(mif\fR.
Thus, the statements
.DS
integer a(3)
Thus, the statements
.DS
integer a(3)
When doing a formatted read of non-character variables,
commas may be used as value separators in the input record,
overriding the field lengths given in the format statement.
When doing a formatted read of non-character variables,
commas may be used as value separators in the input record,
overriding the field lengths given in the format statement.
The simplest is a variable name followed by an equal sign
followed by a data value which is assigned to that variable,
e.g. ``key=5''.
The simplest is a variable name followed by an equal sign
followed by a data value which is assigned to that variable,
e.g. ``key=5''.
The second form consists of an array name followed by ``=''
followed by one or more values to be assigned to the array,
e.g.:
The second form consists of an array name followed by ``=''
followed by one or more values to be assigned to the array,
e.g.:
is the string containing the characters
of the left operand followed by the characters of
the right operand.
is the string containing the characters
of the left operand followed by the characters of
the right operand.
The character expressions
.DS
\(fmab\(fm // \(fmcd\(fm
The character expressions
.DS
\(fmab\(fm // \(fmcd\(fm
rules have been removed.
.B do
loop bounds may be general integer, real, or double precision expressions.
rules have been removed.
.B do
loop bounds may be general integer, real, or double precision expressions.
Computed
.B goto
expressions and \s-1I/O\s0 unit numbers may be general integer expressions.
Computed
.B goto
expressions and \s-1I/O\s0 unit numbers may be general integer expressions.
.\"
.\" %sccs.include.proprietary.man%
.\"
.\"
.\" %sccs.include.proprietary.man%
.\"
-.\" @(#)f77IO.ms 8.2 (Berkeley) %G%
+.\" @(#)f77IO.ms 8.3 (Berkeley) %G%
.\"
.EH 'PSD:9-%''Introduction to the f77 I/O Library'
.OH 'Introduction to the f77 I/O Library''PSD:9-%'
.\"
.EH 'PSD:9-%''Introduction to the f77 I/O Library'
.OH 'Introduction to the f77 I/O Library''PSD:9-%'
only on a unit that can seek. Otherwise tabbing right or spacing with
.B X
will write blanks on the output.
only on a unit that can seek. Otherwise tabbing right or spacing with
.B X
will write blanks on the output.
.Nh 2 "List directed output"
In formatting list directed output, the I/O system tries to prevent
output lines longer than 80 characters.
.Nh 2 "List directed output"
In formatting list directed output, the I/O system tries to prevent
output lines longer than 80 characters.
uses signed arithmetic and such values appear to the arithmetic unit
as negative numbers.
.FE
uses signed arithmetic and such values appear to the arithmetic unit
as negative numbers.
.FE
Radix and ``unsigned'' specifiers could be used to format
a hexadecimal dump, as follows:
Radix and ``unsigned'' specifiers could be used to format
a hexadecimal dump, as follows: