|
|
1.1 root 1: Name
2:
3: shd - Displays named shared memory segments or files in hexadecimal
4: format. Works in both protected mode and real mode with real mode
5: only allowing file examination.
6:
7: Syntax
8:
9: shd [-format] [-mode] [-s offset] [-n count] [name]...
10:
11: Description
12:
13: The shd command displays the contents of named shared memory segments or
14: files in hexadecimal, octal, decimal, and character formats. Control
15: over the specification of ranges of characters is also available.
16:
17: The default behavior is with the following flags set: "-abx -A". This
18: says that address (shared memory or file offsets) and bytes are printed
19: in hexadecimal and that characters are also printed.
20:
21: If no 'name' argument is given, the standard input is read. If one or
22: more names are given, shd first checks to see if 'name' is a valid shared
23: memory segment. If a shared memory segment does not exist, then shd
24: checks for a file with that name. In either case once a valid shared
25: segment or file has been found, all other names on the command line are
26: treated in the same manner as the first.
27:
28: Options include:
29:
30: -s offset
31:
32: Specify the beginning offset in the memory segment or file where
33: printing is to begin. If no memory segment or file argument is
34: given, or if a seek fails because the input is a pipe, 'offset' bytes
35: are read from the input and discarded. Otherwise, a seek error will
36: terminate processing of the current memory segment or file.
37:
38: The offset may be given in decimal, hexadecimal (preceded by '0x'),
39: or octal (preceded by '0'). It is optionally followed by one of the
40: following multipliers: w, l, b, k; for words (2 bytes), long words (4
41: bytes), blocks (512 bytes), or K bytes (1024 bytes). Note that this
42: is the one case where "b" does not stand for bytes. Since specifying
43: a hexadecimal offset in blocks would result in an ambiguous trailing '
44: b', any offset and multiplier may be separated by an asterisk (*).
45:
46: -n count
47:
48: Specify the number of bytes to process. The count is in the same
49: format as offset, above.
50:
51: Mode Flags
52:
53: The mode flags may be used to override the default of checking first
54: for a named shared segment and then for a file that matches the
55: first 'name' argument.
56:
57: -m
58:
59: Sets the mode to named shared memory segments and causes the
60: program to look only for a named shared memory segment and if not
61: found, will not look for a file by the name and will announce
62: that it was not found.
63:
64: -f
65:
66: Sets the mode to files and cause the program to look only for a
67: file and if not found will announce that it was not found.
68:
69: Format Flags
70:
71: Format flags may specify addresses, characters, bytes, words (2
72: bytes), or longs (4 bytes) to be printed in hexadecimal, decimal or
73: octal. Two special formats may also be indicated: text or ASCII.
74: Format and base specifiers may be freely combined and repeated as
75: desired in order to specify different bases (hexadecimal, decimal or
76: octal) for different output formats (addresses, characters, etc.).
77: All format flags appearing in a single argument are applied as
78: appropriate to all other flags in that argument.
79:
80: acbwlA
81:
82: Output format specifiers for addresses, characters, bytes, words,
83: longs and ASCII, respectively. Only one base spec will be used
84: for addresses; the address will appear on the first line of
85: output that begins each new offset in the input.
86:
87: The character format prints printable characters unchanged,
88: special C escapes as defined in the language, and remaining
89: values in the specified base.
90:
91: The ASCII format prints all printable characters unchanged, and
92: all others as a period (.). This format appears to the right of
93: the first of other specified output formats. A base spec has no
94: meaning with the ASCII format. If no other output form at (other
95: than address) is given, bx is assumed. If no base spec is given,
96: all of xdo are used.
97:
98: xdo
99:
100: Output base specifiers for hexadecimal, decimal and octal. If no
101: format spec is given, all of acbwl are used.
102:
103: t
104:
105: Print a text file, each line preceded by the address in the file.
106: Normally, lines should be terminated by a \n character; but long
107: lines will be broken up. Control characters in the range 0x00 to
108: 0x1f are printed as '^@' to '^_'. Bytes with the high bit set
109: are preceded by a tilde (~) and printed as if the high bit were
110: not set. The special characters (^, ~, \) are preceded by a
111: backslash (\) to escape their special meaning. As special cases,
112: two values are represented numerically as '\177 ' and '\377'.
113: This flag will override all output format specifiers except
114: addresses.
115:
116: Names
117:
118: More than one name may be specified in the 'name' argument. There are
119: two formats expected depending on the mode of use.
120:
121: Memory Mode
122:
123: The names listed on the command line must not include the "SHAREMEM\"
124: part of the named shared memory segment. If you want to examine a
125: named shared memory segment it would normally be addressed as:
126: "\SHAREMEM\name.ext" using the standard file naming conventions. This
127: program automatically appends the "\SHAREMEM\" portion of the named
128: shared memory segment and requires that the name argument only
129: include the "name.ext" portion of the named shared memory
130: specification. It will not find the segment if the entire shared
131: memory path is used.
132:
133: File Mode
134:
135: The names listed on the command line may follow the standard file
136: naming conventions with complete path specification as desired.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.