1 :Info: get_object_info: goi: 1982-02-16 get_object_info, goi
2
3 Syntax as a command: goi OBJECT_SEG_PATH KEY
4
5
6 Syntax as an active function: goi OBJECT_SEG_PATH KEY
7
8
9 Function: displays information stored by the compiler or binder in
10 the symbol section of a generated object segment. As an active
11 function, the selected information is returned as a value.
12
13 For information about component objects of a bound segment, use the
14 get_component_info gci command. For details, type: help gci
15
16
17 Arguments:
18 OBJECT_SEG_PATH
19 pathname of the bound or unbound object segment containing the
20 information to be displayed. Archive component pathnames are not
21 supported.
22 KEY
23 specifies the kind of information to display. For a list of
24 supported KEY values, see the "List of keys" section below.
25
26
27 List of keys:
28 Select one key to specify which information is displayed.
29 author, at
30 name and project of the user who compiled or bound the object
31 segment.
32 compiler
33 compiler or binding program that generated the object segment.
34 comment
35 information provided by the compiler or binding program. This is
36 often names the options used when compiling the object segment.
37 date_time_compiled, dtc
38 date and time on which the object segment was generated.
39 options
40 compile or bind options if any were given when the object segment
41 was generated.
42
43
44 version
45 version of the compiler or binding program.
46 primary_source, psc
47 pathname of the main source file compiled to generate the object
48 segment; or main object archive whose components were bound to
49 generate the bound segment.
50 source, sc
51 pathnames of the main source file and include files compiled to
52 generate the object segment; or list of object archives and object
53 segments that were bound to generate the bound object segment.
54
55
56 Examples:
57 goi >t>bound_mbuild_ author
58 Swenson.SysAdmin.a
59
60 goi >t>bound_mbuild_ compiler
61 binder
62
63 goi >t>bound_mbuild_ comment
64
65
66 goi >t>bound_mbuild_ ddate_time_compiled
67 07/26/22 1555.2 pdt Tue
68
69 goi >t>bound_mbuild_ options
70
71
72 goi >t>bound_mbuild_ version
73 Multics Binder, Version 12 of Tuesday, March 26, 1985
74
75 goi >t>bound_mbuild_ primary_source
76 >sysbuild>mcrs>MCR10117>bound_mbuild_.archive
77
78 goi >t>bound_mbuild_ source
79 >sysbuild>mcrs>MCR10117>bound_mbuild_.archive
80
81
82 goi >sl1>active_all_rings_data at
83 Hirneisen.SysMaint.a
84
85 goi >sl1>active_all_rings_data compiler
86 cds
87
88 goi >sl1>active_all_rings_data comment
89
90
91 goi >sl1>active_all_rings_data dtc
92 11/11/89 1037.3 pdt Sat
93
94 goi >sl1>active_all_rings_data options
95
96
97 goi >sl1>active_all_rings_data version
98 create_data_segment_, Version II of Thursday, November 20, 1986
99
100 goi >sl1>active_all_rings_data psc
101 >special_ldd>install>MR12.3-1114>active_all_rings_data.cds
102
103 goi >sl1>active_all_rings_data sc
104 >special_ldd>install>MR12.3-1114>active_all_rings_data.cds
105 >ldd>include>cds_args.incl.pl1
106
107
108 :Info: get_component_info: gci: 1982-02-16 get_component_info, gci
109
110 Syntax as a command: gci OBJECT_SEG_PATH COMPONENT KEY
111
112
113 Syntax as an active function: gci OBJECT_SEG_PATH COMPONENT KEY
114
115
116 Function: displays information stored by the compiler in the symbol
117 section of a component object in a bound object segment. As an active
118 function, the selected information is returned as a value.
119
120 For information about a bound or unbound object segment, use the
121 get_object_info goi command. For details, type: help goi
122
123
124 Arguments:
125 OBJECT_SEG_PATH
126 pathname of the bound object segment containing the component whose
127 information is to be displayed. Archive pathnames and archive
128 component are not supported.
129 COMPONENT
130 objectname of the component object whose information is displayed.
131 Use the print_bind_map pbm command to get a list of components in
132 a given bound segment. For details, type: help pbm
133 KEY
134 specifies the kind of information to display. For a list of
135 supported KEY values, see the "List of keys" section below.
136
137
138 List of keys:
139 Select one key to specify which information is displayed.
140 author, at
141 name and project of the user who compiled or bound the object
142 segment.
143 compiler
144 compiler or binding program that generated the object segment.
145 comment
146 information provided by the compiler or binding program. This is
147 often names the options used when compiling the object segment.
148 date_time_compiled, dtc
149 date and time on which the object segment was generated.
150 options
151 compile or bind options if any were given when the object segment
152 was generated.
153
154
155 version
156 version of the compiler or binding program.
157 primary_source, psc
158 pathname of the main source file compiled to generate the object
159 segment; or main object archive whose components were bound to
160 generate the bound segment.
161 source, sc
162 pathnames of the main source file and include files compiled to
163 generate the object segment; or list of object archives and object
164 segments that were bound to generate the bound object segment.
165
166
167 Examples:
168 gci >t>bound_mbuild_ mbuild author
169 Swenson.SysAdmin.a
170
171 gci >t>bound_mbuild_ mbuild compiler
172 PL/I
173
174 gci >t>bound_mbuild_ mbuild comment
175 optimize
176
177 gci >t>bound_mbuild_ mbuild date_time_compiled
178 12/08/21 1954.8 pdt Wed
179
180
181 gci >t>bound_mbuild_ mbuild options
182 optimize
183
184 gci >t>bound_mbuild_ mbuild version
185 Multics PL/I Compiler, Release 33f, of February 11, 2017
186
187
188 gci >t>bound_mbuild_ mbuild primary_source
189 >sysbuild>mcrs>MCR10102>mbuild.pl1
190
191 gci >t>bound_mbuild_ mbuild source
192 >sysbuild>mcrs>MCR10102>mbuild.pl1
193 >ldd>include>ssu_standalone_command_.incl.pl1
194 >ldd>include>ssu_prompt_modes.incl.pl1
195 >ldd>include>mbuild_Tlist_dcls_.incl.pl1
196 >ldd>include>mbuild_data_.incl.pl
197
198
199 :hcom:
200 /****^ HISTORY COMMENTS:
201 1) change2022-08-02GDixon:
202 A) Initial version of info segment cobbled together from usage line
203 emitted by these commands.
204 2) change2022-08-02GDixon:
205 A) Change gci.info to refer the user to print_bind_map to print a
206 list of components in the bound segment.
207 END HISTORY COMMENTS */
208