Lines Matching full:executable

92 that started the process, commonly a dynamic executable, are applied to the
179 when processing a dynamic executable, any allocated memory that follows the end
209 processing a dynamic executable with the \fBRTLD_MEMORY\fR attribute and allows
210 for reducing the size of the \fIopath\fR disc file. The executable must confine
220 does not provide a panacea for checkpoint and resume. A new dynamic executable,
221 for example, will not start where the original executable called
222 \fBdldump()\fR. It will gain control at the executable's normal entry point.
234 The following code fragment, which can be part of a dynamic executable
252 \fIipath\fR bound to the dynamic executable \fBa.out\fR. All relative
293 The following code fragment, which is part of the dynamic executable
294 \fBa.out\fR, can be used to create a new version of the dynamic executable:
329 Any modifications made to the dynamic executable, up to the point the
331 mechanism allows the executable to update parts of its data segment and heap
332 prior to creating the new object. In this case, the date the executable is
339 information. The elements of the dynamic executable \fIipath\fR that have been
343 dynamic executable to be flexible, and correctly bind and initialize to its
353 initialization requirements, the executable may still only interact correctly
361 within the dynamic executable will have been fixed when it was created by
454 to be a dynamic executable. The dumped object can be processed by the runtime