|
|
1.1 root 1: .TH OD 1 "16 February 83"
2: .UC 4
3: .SH NAME
4: od \- octal, decimal, hex, ascii dump
5: .SH SYNOPSIS
6: .B od
7: [ \-format ] [ file ] [ [\fB+\fP]offset[\fB.\fP][\fBb\fP] [label] ]
8: .SH DESCRIPTION
9: .I Od
10: displays
11: .IR file ,
12: or it's standard input,
13: in one or more dump formats
14: as selected by the first argument.
15: If the first argument is missing,
16: .B \-o
17: is the default.
18: Dumping continues until end-of-file.
19: .PP
20: The meanings of the format argument characters are:
21: .TP 5
22: .B a
23: Interpret bytes as characters and display them with their ACSII names.
24: If the
25: .B p
26: character is given also, then bytes with even parity are underlined.
27: The
28: .B P
29: character causes bytes with odd parity to be underlined.
30: Otherwise the parity bit is ignored.
31: .TP 5
32: .B b
33: Interpret bytes as unsigned octal.
34: .TP 5
35: .B c
36: Interpret bytes as ASCII characters.
37: Certain non-graphic characters appear as C escapes:
38: null=\e0,
39: backspace=\eb,
40: formfeed=\ef,
41: newline=\en,
42: return=\er,
43: tab=\et;
44: others appear as 3-digit octal numbers.
45: Bytes with the parity bit set are displayed in octal.
46: .TP 5
47: .B d
48: Interpret (short) words as unsigned decimal.
49: .TP 5
50: .B f
51: Interpret long words as floating point.
52: .TP 5
53: .B h
54: Interpret bytes as unsigned hexadecimal.
55: .TP 5
56: .B i
57: Interpret (short) words as signed decimal.
58: .TP 5
59: .B l
60: Interpret long words as signed decimal.
61: .TP 5
62: .B o
63: Interpret (short) words as unsigned octal.
64: .TP 5
65: .BR s [n]
66: Look for strings of ascii graphic characters, terminated with a null byte.
67: .I N
68: specifies the minimum length string to be recognized.
69: By default, the minimum length is 3 characters.
70: .TP 5
71: .B v
72: Show all data. By default, display lines that are identical to the last
73: line shown are not output, but are indicated with an ``*'' in column 1.
74: .TP 5
75: .BR w [n]
76: Specifies the number of input bytes to be interpreted and displayed
77: on each output line. If
78: .B w
79: is not specified, 16 bytes are read for each display line.
80: If
81: .I n
82: is not specified, it defaults to 32.
83: .TP 5
84: .B x
85: Interpret (short) words as hexadecimal.
86: .PP
87: An upper case format character implies the long or double precision
88: form of the object.
89: .PP
90: The
91: .I offset
92: argument specifies the byte offset
93: into the file where dumping is to commence.
94: By default this argument is interpreted in octal.
95: A different radix can be specified;
96: If ``\fB.\fR'' is appended to the argument, then
97: .I offset
98: is interpreted in decimal.
99: If
100: .I offset
101: begins with ``\fBx\fP'' or ``\fB0x\fP'',
102: it is interpreted in hexadecimal.
103: If ``\fBb\fP'' (``\fBB\fP'') is appended, the offset is interpreted
104: as a block count, where a block is 512 (1024) bytes.
105: If the
106: .I file
107: argument is omitted, an
108: .I offset
109: argument must be preceded by
110: .RB `` + ''.
111: .PP
112: The radix of the displayed address will be the same as the radix of the
113: .IR offset ,
114: if specified; otherwise it will be octal.
115: .PP
116: .I Label
117: will be interpreted as a pseudo-address for the first byte displayed.
118: It will be shown in ``()'' following the file offset.
119: It is intended to be used with
120: core images to indicate the real memory address.
121: The syntax for
122: .I label
123: is identical to that for
124: .IR offset .
125: .SH "SEE ALSO"
126: adb(1)
127: .SH BUGS
128: A file name argument can't start with ``+''.
129: A hexadecimal offset can't be a block count.
130: Only one file name argument can be given.
131: .PP
132: It is an historical botch to require specification of object, radix, and
133: sign representation in a single character argument.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.